Re: Strange double ACK in TCP/IP

OK ... thanks ... I gather then, that you've affirmed my speculation, and 
that this is not an erroneous behavior.

At 04:49 PM 4/14/2004 -0500, Robert Muchsel wrote:

> > The main difference between the ACKs appears to be in the window frame
> > size. The second one always appears to be a window frame size of 4096, and
> > the first one appears to be the 4096 less the size of the packet actually
> > sent (roughly).
> >
> > Based on this, I would speculate that TINI does an ACK immediately when it
> > receives the packet, telling the sender how much buffer the TINI has left.
> > And then, when my application reads the buffer, TINI sends another ACK to
> > say that it has more buffer space available.
> >
> > Is this what's going on?? Why is the second ACK necessary or desirable???
>
>Since the TINI's TCP buffers are so small, it is highly desirable to let
>the other end of the connection know immediately when there is more room
>in the input buffer. We found that this behavior increases TCP
>throughput when talking to the TINI.
>
>
>--
>   Robert Muchsel - Dallas Semiconductor - http://www.maxim-ic.com/TINI/


vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
: Barry Demchak               :
: Torrey Pines Software, Inc. :
: http://www.tpsoft.com/      :
: (858) 452-8700              :
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 

_______________________________________________
TINI mailing list
TINI-6tN4nzCoH/[email protected]
To UNSUBSCRIBE, edit your profile, or see list archives:
http://lists.dalsemi.com/mailman/listinfo/tini