Francois,
Thanks for your response. I understand what you
are saying, and will change my code accordingly.
However, it occurs to me that a lot of processing
seems to be occurring from the moment the client
arrived until the connection is established and the
OnClientConnect event is fired; and if the client
needs to be dropped for some reason, all this
processing is wasted.
Would it then be a good idea to offer a
cancelling mechanism from the first event that would
skip all the rest? I could work on something if you
think its worth it.
-dZ.
>------- Original Message -------
>From : Francois
PIETTE[mailto:[EMAIL PROTECTED]
>Sent : 10/1/2007 12:35:46 PM
>To : [email protected]
>Cc :
>Subject : RE: Re: [twsocket] Cancelling
TWSocketServer client connection
>
>At the time OnClientCreate is called, the socket is
not assigned yet to the
connection. So it is not easy to cancel the connection.
OnClientConnect is a better place. From there you can
call Shutdown to
terminate the connection you don't want.
Have a look at the source code for
TCustomWSocketServer.TriggerSessionAvailable.
--
[EMAIL PROTECTED]
The author of the freeware multi-tier middleware MidWare
The author of the freeware Internet Component Suite (ICS)
http://www.overbyte.be
----- Original Message -----
--
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
