Hi,

I don't know, specifically.

You will have to do some coding and testing to see if network latency
(includes EVERYTHING, not just the underlying TCP/IP, but other layers, too)
affects your application. I haven't seen a big problem with small packets
myself. However, I have had some applications where is do something like
Nagle in my own software (I use a 50 mS timer), just to reduce my own
packetization/de-packetization overhead.

Dick

--
Richard Grier (Microsoft Visual Basic MVP)

See www.hardandsoftware.net for contact information.

Author of Visual Basic Programmer's Guide to Serial Communications, 3rd
Edition ISBN 1-890422-27-4 (391 pages) published February 2002.

listen_socket.SetSocketOption(SocketOptionLevel.Tcp, SocketOptionName.NoDelay, true)

Disables Nagle algorithm. If you're sending small packets, you might benefit from this

~~K

=?Utf-8?B?S2V2aW4gWiBHcmV5?= <(E-Mail Removed)> wrote
in news:83CD11F8-D202-45A8-94F5-(E-Mail Removed):
> Disables Nagle algorithm. If you're sending small packets, you might
> benefit from this.

1) Should have no effect on UDP since UDP is packet based anyways.

2) NEVER turn off Nagle unless you REALLY REALLY know what you are doing. In
99% of the cases performance will be WORSE.


--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"


ELKNews - Get your free copy at http://www.atozedsoftware.com

Hi Kevin,

Good info.

Thanks, Dick

--
Richard Grier (Microsoft Visual Basic MVP)

See www.hardandsoftware.net for contact information.

Author of Visual Basic Programmer's Guide to Serial Communications, 3rd
Edition ISBN 1-890422-27-4 (391 pages) published February 2002.