lyndon@ncc.UUCP (04/04/87)
In article <122@njitsc1.UUCP>, bc@njitsc1.UUCP (Bill Cheswick) writes: > [...] > And while you are looking for a protocol, how about using one that transmits > files in both directions at the same time? There are many protocols that > have solved this problem already. Actually, the code for the 'g' protocol is very close to this already. By implementing the Selective Reject feature, "piggyback ACKS", and a proper sliding window, the protocol would be capable of handling concurrent bidirectional transfers (I wonder how well the hardware would keep up to this on a PC running at 9600 baud). There are numerous potential side effects involving state synchronization at each end that have not been addressed (to my knowledge) before. There are some nice features that can be adopted from Kermit. The ability to automatically negotiate 7/8 bit data paths is the most obvious, but there are others. With the rapid increase in the volume of net traffic recently, it's probably not to soon to look at on the fly data compression either... -- Lyndon Nerenberg UUCP: {mnetor!seismo, ihnp4, ubc-vision}!alberta!ncc!lyndon {pyramid, winfree}!ncc!lyndon