Re: [twsocket] processmessages or messagepump

2008-07-19 Thread info2004
Arno, Arno Garrels wrote: info2004 wrote: How would I implement a timeout? Do I create a timer component within the thread, or is there a more elegant solution? A timer is ok since your thread processes messages already :-) You could, for example, use an integer that is incremented in

Re: [twsocket] processmessages or messagepump

2008-07-18 Thread info2004
Francois, and Arno, while not terminated do begin WSocket.MessagePump; // check if I need to do something sleep(100); end; // close it all down Or am I missing the point in the use of the message pump? Yes, you miss something. The code you've done will be very slow at processing

Re: [twsocket] processmessages or messagepump

2008-07-18 Thread Fastream Technologies
Why don't you write your own message pump with GetMessage? This way you can process your custom messages as well. Regards, SZ On Fri, Jul 18, 2008 at 10:08 AM, info2004 [EMAIL PROTECTED] wrote: Francois, and Arno, while not terminated do begin WSocket.MessagePump; // check if I

Re: [twsocket] processmessages or messagepump

2008-07-18 Thread Olivier Sannier
Francois PIETTE wrote: So in execute is it Ok to: while not terminated do begin WSocket.MessagePump; // check if I need to do something sleep(100); end; // close it all down Or am I missing the point in the use of the message pump? Yes, you miss something. The code you've

Re: [twsocket] processmessages or messagepump

2008-07-18 Thread Arno Garrels
info2004 wrote: How would I implement a timeout? Do I create a timer component within the thread, or is there a more elegant solution? A timer is ok since your thread processes messages already :-) You could, for example, use an integer that is incremented in timer's event handler and reset it

Re: [twsocket] processmessages or messagepump

2008-07-17 Thread info2004
Arno, So in execute is it Ok to: while not terminated do begin WSocket.MessagePump; // check if I need to do something sleep(100); end; // close it all down Or am I missing the point in the use of the message pump? Regards, Andy Arno Garrels wrote: info2004 wrote: In my thread (I

Re: [twsocket] processmessages or messagepump

2008-07-17 Thread Francois PIETTE
So in execute is it Ok to: while not terminated do begin WSocket.MessagePump; // check if I need to do something sleep(100); end; // close it all down Or am I missing the point in the use of the message pump? Yes, you miss something. The code you've done will be very slow at

Re: [twsocket] processmessages or messagepump

2008-07-17 Thread Arno Garrels
info2004 wrote: Arno, So in execute is it Ok to: while not terminated do begin WSocket.MessagePump; // check if I need to do something sleep(100); end; // close it all down Or am I missing the point in the use of the message pump? This is evil, don't do that, but use

Re: [twsocket] processmessages or messagepump

2008-07-16 Thread Francois PIETTE
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

Re: [twsocket] processmessages or messagepump

2008-07-16 Thread info2004
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?

Re: [twsocket] processmessages or messagepump

2008-07-16 Thread Arno Garrels
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