<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=windows-1252">
<META content="MSHTML 6.00.2800.1264" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>Rene,</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>Thanks for the suggestion. However, in our case our
server may actually be communicating over a wired line in certain scenarios that
are not easily detectable. Globally turning of Nagle would be seriously
detrimental to the wired case, especially when the link is being routed over the
Internet. Beyond throttling, there is the flow-control traffic of TCP
which is very expensive over wireless. These have always been notorious
issues against TCP in wireless scenarios.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><!--StartFragment --> <FONT size=2>Rene Dudfield wrote:</FONT><PRE>Sorry no enet answers.
Have you tried turning off nagle with tcp? Using the socket option TCP_NO_DELAY
Have fun!</PRE></DIV></BODY></HTML>