Some proxies just close or reset the connection if, for instance, the remote server is not listening or if Socks authentication fails for some _technical reason. It's my understanding that in such cases SessionConnected should be triggered with an error > 0 before SessionClose, is that correct? Currently both Socks and HTTP-Tunnel code in TWSocket don't do that but only trigger SessionClose, even without an error in case of close (fin).
Yes, normally in case of a connection cannot be established, OnSessionConnected should be called with a non nul error argument and then OnSessionClosed with same argument.
-- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) 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
