🚀 go-pugleaf

Bob-

Thanks!  I knew I was missing something.  Is t the timeout? What should
thins be initialized as?

-Josh
"Bob Gonder" <notbg@notmindspring.invalid> wrote in message
news:0hvpi29knbm09uif8ncifnmcuihfr6ttsa@4ax.com...
> Josh Arnold wrote:
>
> >My new problem is that when ACK'ing back to the server after receiving
the
> >data, the ACK is taking around 200ms.  Completely unacceptable for the
> >application and I'm obviously doing something wrong.
>
> I'll repost my repost from 1/17/2006
>
>
> See my message from 5/4/2005
> 50th71db9qmpnog2gldkeqvsfv112h3ano@4ax.com
>
> Subject: Re: sendto to same destination more times after eachother
> fails.?
>
> TCP buffers data so the data-to-packetheader ratio is sane. When
> sending a single integer, the packet is several times the size of the
> data, quite wastefull, so by default, TCP holds onto the data for a
> period of time, hoping more data will be sent.
> If you don't want to wait for the timeout, you need to tell TCP not to
> wait.
>
> Look into this WinSock API command, and parameters..
>
> setsockopt(ClientOutSocket,IPPROTO_TCP,TCP_NODELAY,(char*)&t,sizeof(t));
>
>
>