🚀 go-pugleaf

It is non-blocking. As a test I am manually disconnecting the client from 
the Ethernet card.  What I am trying to do is replicate an issue out in the 
field where once in a blue moon I will get an error while sending data to 
the clients which causes an Exception Pointer with SendBuf().  I think it is 
from trying to send out on a socket (client) that is no longer available.

Any insights would be appreciated.

Thanks,

Justin

"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:44ac15e3$1@newsgroups.borland.com...
>
> "Justin L Hudson" <justin.hudson@bepco.com> wrote in message
> news:44ac0064@newsgroups.borland.com...
>
>> Is there a way to make the TimeOut for a 'OnClientDisconnect'
>> to come up faster?
>
> No.
>
>> The situation is, that when I disconnect a Client from the
>> ServerSocket, it takes a good couple of seconds before the
>> 'OnClientDisconnect' is thrown.
>
> Are you using the TServerSocket in non-blocking mode?  If so, then the 
> speed
> of the component is directly related to the speed in which your message
> queue can process new messages.  Non-blocking sockets use window messages
> internally for their asynchronous notifications.  If it is taking so long
> for the event to trigger, then either 1) the message queue is slow, or 2)
> the OS itself is not detecting the disconnect right away to begin with. 
> How
> EXACTLY are you disconnecting the client?
>
>
> Gambit
>
>