Unfortunately in this instance 200mS is a problem. The client is performing
a LIST every 3 seconds on the server. There may be 300-400 files in the
list. All of a sudden the server flags every file as changed and the client
has to download every file to see if the change is valid. So now 200mS per
RETR accumulates to a significant time.
Whereabouts is this code that causes a wait. I would like to experiment with
it.
Regards
Graham
----- Original Message -----
From: "Angus Robertson - Magenta Systems Ltd" <an...@magsys.co.uk>
To: <twsocket@elists.org>
Sent: Friday, October 09, 2009 12:57 PM
Subject: Re: [twsocket] FTP Client Delay - take 2
I am using the ICS FTP client and am experiencing a delay in the
RETR sequence of events. I have attached a Wireshark capture to
demonstrate the problem.
The mailing list does not allow attachments, since they would go to
hundreds of members.
The sequence of events is initially very fast, but after the data
has been received there is a delay of about 200mS while the final
ACKs are sent.
There is some code that causes a wait until the socket has cleanly closed,
to ensure all data is sent OK, is 200ms once per file really an issue?
Angus
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be