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
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
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
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
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
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
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
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
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
Please define local input.
Using the example program ConCli1.dpr
There are better console mode programs. Look at the creation date into the
comments at start of source code. Generally, the more recent, the best !
ConSrv1.dpr is a good one with keyboard interaction.
--
[EMAIL PROTECTED]
(Warning: Old School chatter among us :) )
What I'm wanting to do is write a bbs door game with a tcp client built
in.. Local input (from the door) gets sent across tcp to the server,
which is then relayed to all other nodes.
Basically, real time interbbs.
I'm the developer of Legend of the
There are two other components in the dll which
suffer from the very same
problem. One is the timer and another is one for the
other communication method which
doesn't have a processmessages.
Obviously, you failed to have a working message pump.
Do you have any hints for these as well?
- the receiving TWSocket can't be a static
component on the datamodule
because it has to be in a thread?
Yes, the component has to be _created_ within the context of the thread that
will handle his events.
In case of TWSocket, you have ThreadDetach and ThreadAttach methods if it is
not
15 matches
Mail list logo
