Yes, Shutdown at one side will cause session close at the other side. Actaully, Shutdown is the way to gracefully close a connection. Shutdown send to the other part a close request. The other part respond with a close. The the initiating part call close. This is really the proper way to negociate session end.
-- [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 ----- From: "JLIST" <[EMAIL PROTECTED]> To: <twsocket@elists.org> Sent: Monday, August 11, 2008 12:32 AM Subject: [twsocket] SessionClosed and close/shutdown > Hello all, > > ICS TWSocket only has a SessionClosed event for close of > connection. I suppose a socket.close() from the remote side > (or local) will trigger this event. I wonder if shutdown(0/1/2) > will also trigger the event? For example, a browser using > HTTP/1.0 often sends a request then does a shutdown(1). > Will in this case the ICS server component get a SessionClosed > event? What if it's a shutdown(0) or shutdown(2)? > > -- > Best regards, > Jack > > -- > 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
