Hello Markus,

Since it happen sometimes it is possible you have some where an
exception that does not show up where you loose data.

Other possibility I see you have a long lineEnd. Can you also test with
1 or 2 character? Maybe you have an untested situation.

---
Rgds, Wilfried [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
http://www.mestdagh.biz

Tuesday, May 26, 2009, 22:21, Markus Humm wrote:

> Hello,

>> > after a little reseach and useage of that recommended trial version
>> > found out that the data really gets sent (OnDataSent also triggers).

>> So we are now sure that the issue is probably located in the "other
>> application". The message is sent but that application doesn't see it.
>> How do you know it has not been received ? I mean maybe it is received
>> but
>> actual processingis wrong.
>> Are you able to debug that "other application" ?

> Since I'm the author of both applications I have full source code. What
> a benefit! ;-)

> Ok, the "other" application, in this scenario the server has a
> OnDataAvailable event where the first statement is a OutputDebugString
> command so I can see with Sysinternal's DbgView which messages are
> written and which not. In the good case the message can be seen in the
> bad one it's missing in the debug view so it didn't happen.

> What happens between WinSock and TWSocket? Where could it go lost? It
> hat the correct line end (#7, #8, #9, #0A #0D in my case).

> Any ideas?

> Greetings

> Markus
> --
> 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

Reply via email to