Hello: OnSessionAvailable is triggered when an incoming connection is about to be established, as soon as the request is received, but before the socket is properly opened. OnSessionConnected is triggered right after the connection, either incoming or outgoing, is properly established and state is changed to wsConnected.
If you're not listening on the port, then that could explain why OnSessioinAvailable is not being triggered. You want to handle OnSessionConnected instead. -dZ. >------- Original Message ------- >From : Pete Williams[mailto:[EMAIL PROTECTED] >Sent : 11/28/2007 2:09:51 PM >To : twsocket@elists.org >Cc : >Subject : RE: Re: [twsocket] I need some help understanding TWsocket states > >I don't mind checking simple stuff. I'm desperate, as I have a deadline for Saturday! It is definately connected & hooked-up. Nothing is over-writing it. [EMAIL PROTECTED] wrote: > Hello: > This may sound stupid, but could you verify that > the OnSessionAvailable event is actually wired > (assigned to the property)? It seems strange that it > is not called, yet OnDataSent is. > > Also, what happens when you try to send a second > time (or does it even try)? Do you get a "Component > already connected" error or something like that? > > If your burst messages are short as your example > implies, then there is really no reason to do this on > a separate thread; it will actually be slower to > spawn a new thread and execute it than to just > re-connect and call SendStr. > > -dZ. > > -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
