Wilfried, Erm....Oops. etc.
My debug function to log the timestamps was the culprit. I should have just grabbed the time before, then the time after and done the math. What I actually did was review my log file with timestamps in it. This was the cause of the delay. Using the time before and after the call, I am seeing anything between 15 and 41 ms for the call to return. Not the 300 previously reported. The ICS version is 6.04 according to one of the source files. Regards, Andy Wilfried Mestdagh wrote: > Hello Andy, > >> Dan was correct. The time I noted was for Send to return, not for the data to >> actually be sent. > > Sorry then I have given you a wrong answer. > >> Given the 300ms for Send to return, is this to be expected? > > No it should return immediatly, the function is async. Are you > absolutely sure of this? Do you have a recent version of ICS? > > --- > Rgds, Wilfried [TeamICS] > http://www.overbyte.be/eng/overbyte/teamics.html > http://www.mestdagh.biz > > Thursday, May 15, 2008, 09:09, info2004 wrote: > >> Wilfried, > >> Dan was correct. The time I noted was for Send to return, not for the data to >> actually be sent. > >> Given the 300ms for Send to return, is this to be expected? > >> If it is, then I will look to optimise elsewhere. But it just seems likely >> that >> something is a miss - wrong option setting maybe. > >> Regards, > >> Andy >> Wilfried Mestdagh wrote: >>> Hello Dan, >>> >>>> As far as I know it shouldn't cause the TWSocket send call to take >>>> longer since that is asynchronous >>> Correct, but I think he means the total time to send, not the time of >>> the function call. >>> >>> --- >>> Rgds, Wilfried [TeamICS] >>> http://www.overbyte.be/eng/overbyte/teamics.html >>> http://www.mestdagh.biz >>> > > -- 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