Hello,
> Hello Markus,
>
> > I put some debug output in my OnSessionCLosed handler, it
> doesn't seem to be called.
> > But I haven't yet debugged.
>
> See my other reply. If it is not fired, then eather ShutDown did not
> work because of some exception error, or eather the message
> pump of t
[EMAIL PROTECTED] wrote:
>> I am very confuse, if I need to have a event in the server side to get
>> message sended by clientsocket I need to use de .client.ondataavailable
>> or the server OnDataAvailable event ?
Clients connect to the listening socket of TWSocketServer.
TWSocketServer ac
hi
this question is about your socketspy program since it so nice =)
I was wondering something for what i'm trying to do and that is close remote
socket and keep local connection still alive by not informing it that the
remote socket has closed. I am doing it like this and commenting out the
sessio
I am very confuse, if I need to have a event in the server side to get
message sended by clientsocket I need to use de .client.ondataavailable
or the server OnDataAvailable event ?
- Original Message -
From: "Wilfried Mestdagh" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sen
Hello Markus,
> I will check next the thread ids as recommendet by somebody else.
Also you need to check if the message pump is working in the right
thread context. So you best check over there too. This because you
mention that OnClose is never fired. I think I forgot to say that in my
previous
> thanks for clarification. It doesn't matter that the one thread which
> communicates via TWSocket doesn't reside in the same DLL as the TWSocket
> created?
A thread is not located in a DLL or in an exe. A thread is independent on
where the code is !
Putting a method into a TThread class doesn't
>> Yes because you don't need threads with ICS :) you can easily exchange
>> data with multiple concurent at the same time.
>
> Yes I can, I know. But that doesn't multiply my capacity for
> simultaniously
> processing the packets. I split it up into this threaded scenario because
> data processin
>> HM> while (GetTickCount-t < 100) do
>> HM> begin
>> HM> TranslateMessage(MsgRec);
>> HM> DispatchMessage(MsgRec);
>> HM> WaitMessage;
>> HM> end;
This doesn't look like a proper message loop.
Waiting 100mS for shutdown to complete is probably much much too short !
--
[EMAIL P
> Hello Markus,
>
> Seems you don't get the Event-driven way of programming, why a loop of
> 100ms that seems to do nothing with event it could receive ?
>
> HM> - output a debug message to eventlog
> HM> - socket.shutdown(1);
> HM> - output a 2nd message to eventlog
> HM> - do this:
> HM> t:=G
Hello,
> Hi Marcus,
>
> I've been following your problem and I believe that the
> problem you have
> is because you are trying to use a dll with only a little
> multi-threading experience. One of the reasons people avoid threads is
> that it requires a lot of reading, development time,
> experi
Hello Markus,
> I put some debug output in my OnSessionCLosed handler, it doesn't seem to be
> called.
> But I haven't yet debugged.
See my other reply. If it is not fired, then eather ShutDown did not
work because of some exception error, or eather the message pump of the
thread where TWSocket
Hello,
I put some debug output in my OnSessionCLosed handler, it doesn't seem to be
called.
But I haven't yet debugged.
Greetings
Markus Humm
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at ht
Hello Markus,
Seems you don't get the Event-driven way of programming, why a loop of
100ms that seems to do nothing with event it could receive ?
HM> - output a debug message to eventlog
HM> - socket.shutdown(1);
HM> - output a 2nd message to eventlog
HM> - do this:
HM> t:=GetTickCount;
HM> w
Hello Markus,
> How can I solve my problem? Which thread does the socket belon to
> now? Does it belong to the thread in
Use GetCurrentThreadID to find out the thread context of the code.
Check this where the TWSocket is created and where you Destroy it. Check
this also in some of the TWSocket e
Hello,
I did some changes now (I will onl make changes to my communication dll
which don't affect the other communication methods).
I derrived a descendant from TWSocket which implements the OnSessionClosed
method
and overrides create to assign my OnSessionClosed variant to the property.
In my
Hi Marcus,
I've been following your problem and I believe that the problem you have
is because you are trying to use a dll with only a little
multi-threading experience. One of the reasons people avoid threads is
that it requires a lot of reading, development time, experience and when
something go
16 matches
Mail list logo
