I solved the problem now (at least mostly) by creating a thread and
assigning the socket to this thread. The execute of the thread is mostly
a message loop.
The normal case now behaves as it should, but if I try to handle a
"emergency" exit command (means not the normal way to quit but some
allow
Hello,
I solved the problem now (at least mostly) by creating a thread and
assigning the socket to this thread. The execute of the thread is mostly
a message loop.
The normal case now behaves as it should, but if I try to handle a
"emergency" exit command (means not the normal way to quit but som
> 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 miss
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://
> > > 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 d
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.
>
--
francois.pie...@overbyte.be
The author of the freeware multi-tier middleware MidWare
The author of the freeware Internet Component Suite (ICS)
http://www.overbyte.be
- Original Message -
From: "Markus Humm"
To: "ICS support mailing"
Sent: Tuesday, May 26, 2009 6:36
Hello,
after a little reseach and useage of that recommended trial version I
found out that the data really gets sent (OnDataSent also triggers).
It simply doesn't trigger OnDataAvailable on the server side without
known reason. There is a 2nd TCP connection which is quite similar
constructed and
Hello Markus,
> problem here is: it's a connection to 127.0.0.1 which at least Wireshark
> doesn't see. Can you recommend any other packet sniffer capable of
> watching localhost connections?
You can use SocketSpy (you can find it at the user made page). It works
like a kind of proxy dislaying al
You may use the evaluation version of CommView to capture localhost connections.
See http://www.tamos.com/products/commview/
hope this help
On Mon, May 25, 2009 at 3:04 PM, Markus Humm wrote:
>> You should use a network monitor (packet sniffer) to see if your message is
>> sent or not accross th
> You should use a network monitor (packet sniffer) to see if your message is
> sent or not accross the network. You'll then be able to understand if the
> problem is the sending side or the receiving side.
>
> Most of the time, transmission doesn't work when the message pump is no more
> calle
To: "ICS support mailing"
Sent: Monday, May 25, 2009 8:33 PM
Subject: Re: [twsocket] TWSocket doesn't always send my data?
Hello,
today I rewrote that part of the application but without success.
It now works like this: the GUI finds that the user wants to quit.
OnCloseQuery i
Hello,
today I rewrote that part of the application but without success.
It now works like this: the GUI finds that the user wants to quit.
OnCloseQuery is called. Here a custom message (wm_user+100) is sentm, a
flag is set and can close is set to false. In ApplicationMessages the
GUI calls a com
Sent: Wednesday, May 20, 2009 8:12 PM
Subject: [twsocket] TWSocket doesn't always send my data?
> Hello,
>
> I'm using V5's TWSocket in D2007 and have a strange problem which
> doesn't always occur but approx. 2-3 times out of 10 tries.
>
> I have two applic
Hello,
I'm using V5's TWSocket in D2007 and have a strange problem which
doesn't always occur but approx. 2-3 times out of 10 tries.
I have two applications running on the same PC "connected" via a
TWSocket TCP connection (127.0.0.1). The client side is in a COM
automation DLL (I think single th
15 matches
Mail list logo