Hello Francois, I called CloseAsync() in OnRequestDone. However, CloseAsync() seems to be triggering another OnRequestDone and causing a endless loop ... I tried both cases of the remote IP being available and unavailable (OnRequestDone returns an error in this case.)
Is it necessary to call CloseAsync() in OnRequestDone? What exactly is CloseAsync() for? -- Best regards, Jack Thursday, October 20, 2005, 2:39:26 AM, you wrote: >> I'm using httpcli in async mode. >> Should I use httpcli.Close() or httpcli.CloseAsync()? > CloseAsync > -- > Contribute to the SSL Effort. Visit > http://www.overbyte.be/eng/ssl.html > -- > [EMAIL PROTECTED] > Author of ICS (Internet Component Suite, freeware) > Author of MidWare (Multi-tier framework, freeware) > http://www.overbyte.be > ----- Original Message ----- > From: "Jack" <[EMAIL PROTECTED]> > To: "ICS support mailing" <twsocket@elists.org> > Sent: Thursday, October 20, 2005 12:22 AM > Subject: [twsocket] Async http, close or closeAsync? >> Hello all, >> >> I'm using httpcli in async mode. Since I'm using http 1.0, >> most likely the server will disconnect when it's done sending >> the data. I just want to be sure so I plan to disconnect in >> HttpCliRequestDone event handler. Should I use httpcli.Close() or >> httpcli.CloseAsync()? >> >> Thanks. >> -- >> Best regards, >> Jack >> >> -- >> 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
