> > 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 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
[EMAIL PROTECTED] wrote:
> Here's a sample of my code:
>
> Procedure TMyServer.ClientDataAvailable(Sender:
> TObject; Error: Word);
> Begin
> With (Sender As TMyClient) Do Begin
> If (SomethingBadHappened) Then Begin
> SendLine('Error!');
> Shutdown(1);
> End;
> End;
> End;
TECTED]:[EMAIL PROTECTED]
>Sent: 10/17/2007 2:36:00 PM
>To : twsocket@elists.org
>Cc :
>Subject : RE: Re: [twsocket] TWSocketServer
Client.Shutdown(1) does not destroy it
>
>Hello:
Its worse... I also noticed that
TWSocketClient.TriggerSessionClosed() is triggere
:
>Subject : RE: [twsocket] TWSocketServer
Client.Shutdown(1) does not destroy it
>
>Hello:
I just started noticing this behaviour today, and
I seem to recall it working differently: When
handling the OnClientDataAvailable event, if I
determine that the client needs to be di
Hello:
I just started noticing this behaviour today, and
I seem to recall it working differently: When
handling the OnClientDataAvailable event, if I
determine that the client needs to be disconnected, I
call (Sender As TMyClient).Shutdown(1). The
connection is dropped fine, but the client obj
