[EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Friday, June 23, 2006 9:12 PM
Subject: Re: [twsocket] V6 ThreadDetach #2
Francois PIETTE wrote:
You get the session closed after calling ThreadDetach ?
Yes, since I'm always stress testing. A client may disconnect at
any
: [twsocket] V6 ThreadDetach #2
Arno Garrels wrote:
Francois PIETTE wrote:
Not sure what you mean. The problem is that even if you call
ThreadDetach (which is to make the component windowless) you cannot
be sure that the component will not allocate another window handle
somewhere
-
From: Arno Garrels [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Thursday, June 22, 2006 9:37 PM
Subject: Re: [twsocket] V6 ThreadDetach #2
Arno Garrels wrote:
Francois PIETTE wrote:
Not sure what you mean. The problem is that even if you call
ThreadDetach
PROTECTED]
http://www.overbyte.be
- Original Message -
From: Arno Garrels [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Friday, June 23, 2006 8:55 AM
Subject: Re: [twsocket] V6 ThreadDetach #2
Already got it! It is as I wrote in my previous mail...
procedure
--
[EMAIL PROTECTED]
http://www.overbyte.be
- Original Message -
From: Arno Garrels [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Friday, June 23, 2006 8:55 AM
Subject: Re: [twsocket] V6 ThreadDetach #2
Already got it! It is as I wrote in my previous mail
I have the following problem in V6:
constructor TListenThread.Create(AServer: TMtWSocketServer);
begin
inherited Create(True);
FreeOnTerminate := FALSE;
FServer := AServer;
FServer.ThreadDetach;
end;
procedure TListenThread.Execute;
begin
FServer.ThreadAttach;
support mailing twsocket@elists.org
Sent: Thursday, June 22, 2006 3:20 PM
Subject: [twsocket] V6 ThreadDetach #2
I have the following problem in V6:
constructor TListenThread.Create(AServer: TMtWSocketServer);
begin
inherited Create(True);
FreeOnTerminate := FALSE;
FServer
-
From: Arno Garrels [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Thursday, June 22, 2006 3:20 PM
Subject: [twsocket] V6 ThreadDetach #2
I have the following problem in V6:
constructor TListenThread.Create(AServer: TMtWSocketServer);
begin
inherited Create
: Thursday, June 22, 2006 4:20 PM
Subject: [twsocket] V6 ThreadDetach #2
:I have the following problem in V6:
:
: constructor TListenThread.Create(AServer: TMtWSocketServer);
: begin
:inherited Create(True);
:FreeOnTerminate := FALSE;
:FServer := AServer
and btnStop.
Regards,
SZ
- Original Message -
From: Arno Garrels [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Thursday, June 22, 2006 4:20 PM
Subject: [twsocket] V6 ThreadDetach #2
I have the following problem in V6:
constructor TListenThread.Create(AServer
Sent: Thursday, June 22, 2006 4:20 PM
Subject: [twsocket] V6 ThreadDetach #2
I have the following problem in V6:
constructor TListenThread.Create(AServer: TMtWSocketServer);
begin
inherited Create(True);
FreeOnTerminate := FALSE;
FServer := AServer
, June 22, 2006 4:20 PM
Subject: [twsocket] V6 ThreadDetach #2
I have the following problem in V6:
constructor TListenThread.Create(AServer: TMtWSocketServer);
begin
inherited Create(True);
FreeOnTerminate := FALSE;
FServer := AServer;
FServer.ThreadDetach;
end
]
To: ICS support mailing twsocket@elists.org
Sent: Thursday, June 22, 2006 6:59 PM
Subject: Re: [twsocket] V6 ThreadDetach #2
Fastream Technologies wrote:
I had the same problem. In my case, I had to post a message before
ending the thread. There was pending messages that called GetHandle
: Thursday, June 22, 2006 8:01 PM
Subject: Re: [twsocket] V6 ThreadDetach #2
Francois PIETTE wrote:
This is surely not the problem, but WaitFor should be avoided when
possible. It is known to create deadlocks.
I already exchanged it by a simple WaitForSingleObject(ThreadHandle)
since WaitFor
22, 2006 8:01 PM
Subject: Re: [twsocket] V6 ThreadDetach #2
Francois PIETTE wrote:
This is surely not the problem, but WaitFor should be avoided when
possible. It is known to create deadlocks.
I already exchanged it by a simple WaitForSingleObject(ThreadHandle)
since WaitFor is know
Not sure what you mean. The problem is that even if you call ThreadDetach
(which is to make the component windowless) you cannot be sure that the
component will not allocate another window handle somewhere in the
background
after that call to ThreadDetach.
I don't see how the component
Francois PIETTE wrote:
Not sure what you mean. The problem is that even if you call
ThreadDetach (which is to make the component windowless) you cannot
be sure that the component will not allocate another window handle
somewhere in the background
after that call to ThreadDetach.
I don't
Arno Garrels wrote:
Francois PIETTE wrote:
Not sure what you mean. The problem is that even if you call
ThreadDetach (which is to make the component windowless) you cannot
be sure that the component will not allocate another window handle
somewhere in the background
after that call to
18 matches
Mail list logo
