"zing" <zi**********@hotmail.com> wrote in message
news:11**********************@v46g2000cwv.googlegr oups.com...
Our company is in the startup phase of a large project involving lots
of network traffic. At this point, I'm trying to find out whether TCP
will be fast enough for the task. I've read a few articles that promote
UDP, claiming that TCP is slow, mainly written by gamers. But I've also
read some articles by more scientific sources, which made it clear that
a lot of progress has been made during the last 15 years or so. I
actually find it quite hard to believe that TCP should be slow, unless
an algorithm from the early 90's is used.
My question is: can anyone tell me what TCP-algorithm is used by dotnet
(For example TCP-Reno, TCP-Vegas, or maybe an even more recently
developed algorithm ?)
This does not depend on .NET framework, but rather on operating system. TCP
is not slow by definition, however if you need fine controll over timeouts
or improvements based on you specific netwerk requirements (TCP is general
purpose protocol) UDP offers much finer control. You have to implement flow
control, congestion control and error correction/retransmission yourself if
you use UDP (all come free with TCP). There are some parameters of TCP which
are configurable through socket interface, some through registry. TCP
registry parameters should not be changed by user application, which may
represent a problem.
There was a document on Microsoft site describing TCP/IP implementation in
w2k. As far as I rememeber, it was newer version of protocol with SACK
(selective acknowledgements).
Regards,
Goran