On 16 Mar 2001, Rich Salz <[EMAIL PROTECTED]> wrote: > > Here's my current idea: it may be na?ve about the TCP bugs, but I hope > > it will be more reliable and still keep both directions on the network > > maximally full. > > You owe it to yourself to look at BEEP and the TCP mapping. It was > designed by folks who really know how to optimize ietf-style protocols. > Sliding windows, sequence numbers, all that good stuff. I know it's a good design, and I've read the spec already. I'm just not sure that we need a whole other set of sliding windows etc on top of TCP if TCP is already sufficient. > I believe they're RFC's now. Also read the draft-mrose-beep-design > Internet-Draft. The draft-mrose-beep-design document is a very nice analysis. I'm reading it now. I wonder if adding two-way communications rather than request/response would be a good thing? It might take rsync into an interesting space for push-replication. -- Martin Pool, Human Resource Linuxcare. Inc. +61 2 6262 8990 [EMAIL PROTECTED], http://linuxcare.com.au/ Linuxcare. Putting Open Source to work.
