On 4/1/06, Matthew Kaufman <[EMAIL PROTECTED]
> wrote:
I agree. I suggested getting rid of resends and selective acks via coding,
not ditching congestion control altogether. Coding can get rid of ack
packets that often carry just a tiny bit of information. And it solves his
problem of what resend timeout parameters to pick. We know too little
about Lemon's system to jump to any conclusions about congestion
control - for all I know, it's a point-to-multipoint system with built-in
throttling.
Sounds cool, does it work on Linux?
Forward error correction has its place, but it is no excuse for eliminating
the feedback necessary to perform proper congestion control.
I agree. I suggested getting rid of resends and selective acks via coding,
not ditching congestion control altogether. Coding can get rid of ack
packets that often carry just a tiny bit of information. And it solves his
problem of what resend timeout parameters to pick. We know too little
about Lemon's system to jump to any conclusions about congestion
control - for all I know, it's a point-to-multipoint system with built-in
throttling.
My personal (albeit biased) suggestion is to use amicima's MFP, which gets
you congestion controlled delivery for both reliable *and* unreliable flows,
among many other features.
Sounds cool, does it work on Linux?
Bob.
_______________________________________________ p2p-hackers mailing list p2p-hackers@zgp.org http://zgp.org/mailman/listinfo/p2p-hackers _______________________________________________ Here is a web page listing P2P Conferences: http://www.neurogrid.net/twiki/bin/view/Main/PeerToPeerConferences
