very high latency network problem : 2

"Fred M Goolsby" <fmgoolsb-5wfLAf0ZXl5/[email protected]>
Newsgroups gmane.comp.hardware.microcontrollers.tini
Message-ID <[email protected]>

Sorry to repost this but I got no responce the first time I posted this
back in december.

It appears that TINI TCP/IP does not follow the Geometric Backoff algorithm
for the retransmit timer.  This has not been a problem until
we started dealing with VERY SLOW networks (800 - 900 ms latency).

Has anyone dealt with anything similar to this?  Is there any workaround
short of switching from TCP to UDP ?

----- repost from original message--------
>I am writing a client/server application that does network io at the
socket level.  I am going over a very high latency
>(1000+ milisecond) network.
>
>The application fails with an IO exception.  I know it is not an
application problem since I can duplicate the same error with
>the Slush FTP command if the ftp server is also across the same slow link.
>
>I can sniff the connection and see an outbound packet.  After about 450
ms, having not seen a TCP ack from the receiver, the
>TINI (assuming the packet was lost ?) retransmits the packet a second
time.  After another 450 ms, a third retransmission. And after a third 450
ms the >TINI shuts down the window (accepting no more data).  We then see
the ack from the original packet but the port is now closed.
>
>Duplicating this from a laptop, we see the second and third wait times
extending to 2,4, and 8 seconds.
>
>I am developing with 1.02f but I have duplicated the problem via FTP with
1.11.  I have not tried any OS newer than 1.11 but the release notes for
the >new releases don't appear to address any related issue.


Thank you.
Fred


_______________________________________________
TINI mailing list
TINI-6tN4nzCoH/[email protected]
To UNSUBSCRIBE, edit your profile, or see list archives:
http://lists.dalsemi.com/mailman/listinfo/tini
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.