#> HELLO WORLD.
Is the list working...?
Please ignore this message.
-dZ.
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
> Do you see similar (strange delays or high CPU use) with IE or any
> other internet application as well?
Delays, yes. CPU use, no. But that is an interesting idea, I could
try the same thing on different PCs.
IE has its own problems. Applications that depend on IE can stall
each other. For exa
> > Your code does not guarantee that all data will be sent
> > to the client. Make sure that ShutDown() is called after
> > all data has been delivered to winsock. Something like
> > that:
> Thanks Arno. But now I'm confused: It was because I was told to call
> Shutdown(1) that I used it when c
DZ-Jay wrote:
> On Oct 18, 2007, at 02:35, Arno Garrels wrote:
>
>> Your code does not guarantee that all data will be sent
>> to the client. Make sure that ShutDown() is called after
>> all data has been delivered to winsock. Something like
>> that:
>
> Thanks Arno. But now I'm confused: It wa
On Oct 18, 2007, at 05:36, Ana Onarres wrote:
> I am confused. Clients is the property of TWSocketServer, not of
> ClientThread. ClientThread extends TThread, for controling every
> connection, every client socket.
Anne,
I was talking about the TWSocketThrdServer, not the TWSocketServe
On Oct 18, 2007, at 02:35, Arno Garrels wrote:
> Your code does not guarantee that all data will be sent
> to the client. Make sure that ShutDown() is called after
> all data has been delivered to winsock. Something like
> that:
Thanks Arno. But now I'm confused: It was because I was told to c
Hello,
I am confused. Clients is the property of TWSocketServer, not of ClientThread.
ClientThread extends TThread, for controling every connection, every client
socket. If the server has connected three clients, is there 3 TThrdSrvClient or
3 ClientThread?
TThrdSrvClient is:
TThrdSrvClient
Tobias Giesen wrote:
> Hello,
>
> thanks for the suggestions, Arno and Francois!
>
> I will try it using ASync calls. I tried ftpWaitUsingSleep but it does
> not make any difference.
>
> But the problem is not a CPU concurrency problem. It is much worse.
> The main thread calls PeekMessage (in T
