Thank you very much to all !
As a first try, I will go to the mono thread. Using the same
--
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
Sorry - I pressed the wrong key :-)
Thank you very much to all !
As a first try, I will go to the mono-thread route. Using the same event
handlers is a huge improvement to my initial idea.
Angus : I will take a look at your program, that may help a lot. Thank you.
Arno : I will do some extensive
Hi,
In my thread (I know, you don't need threads...), in the execute procedure,
should I call WSocket.ProcessMessages, or WSocket.MessagePump?
Are they the same? If not, what is the difference?
Thanks,
Andy
--
To unsubscribe or change your settings for TWSocket mailing list
please goto
In my thread (I know, you don't need threads...), in the execute
procedure,
should I call WSocket.ProcessMessages, or WSocket.MessagePump?
Are they the same? If not, what is the difference?
No, they are not the same.
Have a look at the source code and the comments in the source code. They
Hi again,
When I got my grep correct, I found it in WSocket.pas.
Looks like they are the same when multithreaded is true.
...Andy
info2004 wrote:
Hi,
In my thread (I know, you don't need threads...), in the execute procedure,
should I call WSocket.ProcessMessages, or WSocket.MessagePump?
info2004 wrote:
In my thread (I know, you don't need threads...), in the execute
procedure, should I call WSocket.ProcessMessages, or
WSocket.MessagePump?
TWSocket.ProcessMessages processes pending messages once and returns.
You should call TWSocket.MessageLoop instead since it waits for
