> If one were to use WSocketServer to handle multiple client connections
> simultaneously, what would be the preferred method to stop the server
> and therefore close all client connections?
Closing the server socket doesn't break any existing connection, it just
make the server stop accepting new
Isn't it possible to implement it in V5 also ?
Paul
- Original Message -
From: "Arno Garrels" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Wednesday, March 21, 2007 11:49 AM
Subject: Re: [twsocket] ICS bug ?
> Arno Garrels wrote:
>>
>> It's a known issue, we discussed already
If one were to use WSocketServer to handle multiple client connections
simultaneously, what would be the preferred method to stop the server
and therefore close all client connections?
Also, this is assuming that the server will re-activate again later
while the application continues to run the who
We don't need a component at all. We can call the API (like UpdateTimer) in
your code and use the component hidden window. There is no conflict possible
with the WM_TIMER message.
--
Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html
--
[EMAIL PROTECTED]
http://www.overbyte.
Francois Piette wrote:
Don't use TTimer in any worker thread since it is NOT thread-safe!
>>>
>>> Why is it used in HttpCli then ?
>>> see THttpCli.SendRequest
>>
>> That's true, I would not define UseBandwidthControl in multithreaded
>> applications until a thread-safe timer becomes availab
> >> Don't use TTimer in any worker thread since it is NOT thread-safe!
> >
> > Why is it used in HttpCli then ?
> > see THttpCli.SendRequest
>
> That's true, I would not define UseBandwidthControl in multithreaded
> applications until a thread-safe timer becomes available.
We could use a bare b
Paul wrote:
>> Don't use TTimer in any worker thread since it is NOT thread-safe!
>
> Why is it used in HttpCli then ?
> see THttpCli.SendRequest
That's true, I would not define UseBandwidthControl in multithreaded
applications until a thread-safe timer becomes available.
--
Arno Garrels [TeamIC
Paul wrote:
> in which line should this be added ?
Add it below:
"// Make FReceiveBuffer at least 8KB larger than actually received data"
>
> Paul
>
>
> - Original Message -
> From: "Arno Garrels" <[EMAIL PROTECTED]>
> To: "ICS support mailing"
> Sent: Wednesday, March 21, 2007 11:46
Have to switch back then.
Paul
- Original Message -
From: "Arno Garrels" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Wednesday, March 21, 2007 11:49 AM
Subject: Re: [twsocket] ICS bug ?
> Arno Garrels wrote:
>>
>> It's a known issue, we discussed already in the SSL-List.
>
in which line should this be added ?
Paul
- Original Message -
From: "Arno Garrels" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Wednesday, March 21, 2007 11:46 AM
Subject: Re: [twsocket] ICS bug ?
> Paul wrote:
>> Since I updated to the latest ICS version (V5), I sometimes ge
> Don't use TTimer in any worker thread since it is NOT thread-safe!
Why is it used in HttpCli then ?
see THttpCli.SendRequest
Paul
- Original Message -
From: "Arno Garrels" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Wednesday, March 21, 2007 8:32 AM
Subject: Re: [twsocket]
Hello!
I just noticed that I'm getting an empty error message (property
tFtpClient.ErrorMessage) when making an attempt to move a non-existing
file to the peer with Put().
The problem seems to be that a "SetErrorMessage" statement is missing in
the TCustomFtpCli.DoPutAppendAsync procedure. In my
Arno Garrels wrote:
>
> It's a known issue, we discussed already in the SSL-List.
Please forget my last message it applies to V6 only.
--
Arno Garrels [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
--
To unsubscribe or change your settings for TWSocket mailing list
please goto htt
Paul wrote:
> Since I updated to the latest ICS version (V5), I sometimes get an
> exeption when closing my program : EOSError (code 14000) Invalid
> window handle. I can't trap the error, it happens after all events
> are handled. I've just had it again within the debugger, but it fails
> to step
Since I updated to the latest ICS version (V5), I sometimes get an exeption
when closing my program :
EOSError (code 14000) Invalid window handle.
I can't trap the error, it happens after all events are handled.
I've just had it again within the debugger, but it fails to step to the next
instruct
Markus Humm wrote:
> Hello,
>
> regarding my question from last weekend only a part was answered so
> far. The thing is now: if several TTimers get fired at the same time
> and all of them want to write into a shared TStringList-Type buffer
> (okay, it's in a wrapper class), how to make sure only
16 matches
Mail list logo
