> Why is there a RequestDone event while the StatusCode is still zero > anyway?
I would be interested in finding a reproductible case where it occurs. -- [EMAIL PROTECTED] http://www.overbyte.be ----- Original Message ----- From: "Merijn Terheggen" <[EMAIL PROTECTED]> To: "ICS support mailing" <twsocket@elists.org> Sent: Saturday, July 23, 2005 6:04 PM Subject: [twsocket] HttpCli StatusCode = 0 causes problems >I noticed some behavior of HttpCli that caused me a LOT of headaches > before I discovered what was going on and made a work-around. > > This mail is to ask you: > - If the behavior that I noticed indeed happens the way I describe > - If the behavior is consiously designed this way or needs to be changed > > On the RequestDone event, the StatusCode can be 0. I only notice this > happen rarely in certain cases of a redirect (FollowRelocation set to > 'true'). If I've seen things correct, there can be ANOTHER RequestDone > event following in this case. > > Why is this a problem? The RequestDone event is typically used to > process the HttpCli data. After processing, the client potentially > could get deleted since it has no function anymore (as happens in my > code at least). However, another RequestDone event following the first > one when the client has been deleted already causes access violations > etc. > > The only way to be sure the RequestDone event is the 'final' event > seems to be a check on the StatusCode. In case the StatusCode = 0, I > let the event handler return because another RequestDone event will > follow. > > Why is there a RequestDone event while the StatusCode is still zero > anyway? > > Thanks, > > --Merijn > -- > 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
