Unfortunately it turned out that it is still buggy and reusing of ThttpCli::HEADAsync is problematic after an abort. I am not sure how I can demostrate this to you and open to ideas...
Best Regards, SZ ----- Original Message ----- From: "Fastream Technologies" <[EMAIL PROTECTED]> To: "ICS support mailing" <[email protected]> Sent: Tuesday, August 29, 2006 7:12 PM Subject: Re: [twsocket] Need help with THttpCli reuse after abort() : Hi, : : I found out that calling cleanrcvdstreams() and cleansentstreams() killed : the problem. FYI, I also called InternalClear() after each abort. : : Thanks, : : SZ : : P. S. Francois, I see that my first private message has been received by you : but my second reply message is again bounced... Strange, isn't it?! : : ----- Original Message ----- : From: "Fastream Technologies" <[EMAIL PROTECTED]> : To: "ICS support mailing" <[email protected]> : Sent: Tuesday, August 29, 2006 10:55 AM : Subject: Re: [twsocket] Need help with THttpCli reuse after abort() : : :: Hello, :: :: I really think the problem is with the HEAD command and component reuse :: after abort(). It works fine with GET but for the cache validation, we : need :: the HEAD first. :: :: Hope you can help, :: :: SubZero :: :: ----- Original Message ----- :: From: "Fastream Technologies" <[EMAIL PROTECTED]> :: To: "ICS support mailing" <[email protected]> :: Sent: Tuesday, August 29, 2006 10:30 AM :: Subject: [twsocket] Need help with THttpCli reuse after abort() :: :: ::: Hello, ::: ::: As you know I am coding a reverse proxy. In my proxy, I am keeping HTTP ::: CLIENT connections open after a request so that the next request does not ::: wait for the establishment. Now, when something goes wrong (i.e. socket ::: error), I abort the client connection as well to reset the internal state ::: machine. However, when I do so, in the next request, (which needs to :: reopen ::: the socket) it stalls at SocketDataAvailable. It goes to : httpwaitingheader ::: part but reads data instead of header and cannot find the #10 so exits. :: This ::: was not the case when we did not have a cache and did not feel the need : to ::: send HEAD command before GET. Now it stalls at HEAD!! ::: ::: Any idea? ::: ::: Best Regards, ::: ::: SZ ::: ::: -- ::: 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 :: :: -- :: 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 : : -- : 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 -- 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
