Hello, > Hello Markus, > > > I put some debug output in my OnSessionCLosed handler, it > doesn't seem to be called. > > But I haven't yet debugged. > > See my other reply. If it is not fired, then eather ShutDown did not > work because of some exception error, or eather the message > pump of the > thread where TWSocket is created or attached to is not pumping.
Okay, exception can be ruled out, the shutdown call is within try / except and I have a output in the except clause showing the exception. This doesn't fire. Another thought: the dll has a seperate thread only for message pumping for all used components within the dll. What if I would assign all sockets to this thread after creation? e.g. assign the sockets to this thread when they're created and give the thread a method for closing these sockets. Could this solve my problems? Greetings Markus -- 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
