Francois, See my post, it is not sufficient to use OnRequestDone. There might still be messages pending in case of abort/network error when SetReady is called twice!
Regards, SZ On Sun, Oct 19, 2008 at 11:34 AM, Francois PIETTE <[EMAIL PROTECTED] > wrote: > > I am using a httpcli created on run-time. I first connect to a website, > > and after DocEnd I call another procedure that changes the event > > procedures and connects to a different website. On the 2nd call I get an > > Exception "HTTP component is busy", so I do this before trying the 2nd > > call > > > > try > > LoginSocket.Abort; > > except > > end; > > > > that, however, generates another exception. Checking the httpcli state > > before the abort, it is "Waiting Body" > > > > What is the best way to "reset" the component between both calls and > leave > > it in a "Ready" state? The first call is GetAsync and the 2nd one is > > PostAsync. > > Do not use OnDocEnd to start the next connection but OnRequestDone. > OnDocEnd is when the document is complete (Time to commit in database for > example) while OnRequestDone tells you the component has finished your > request and is ready for the next one. > > -- > [EMAIL PROTECTED] > 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
