Hello Arno, The reason is when the state is httpReady, it is not yet ready in some cases, that is a misleading state machine state (IMHO).
ASAP I will try the postmessage and let you know if it is ok for my case here. I believe I did this a few weeks ago but not sure so will retry in case... Thanks, SZ On 5/16/09, Arno Garrels <arno.garr...@gmx.de> wrote: > Fastream Technologies wrote: > > What about setting a flag in triggerrequestdone and then checking for > > it with while loop just as we do now for httpready in Dorequestsync? > > This would eliminate the issue and let us use both sync and async > > together! > > Sounds like more bad design IMO. Why can't you use either sync or > async methods? Or why not just post a custom message from OnRequestDone? > > > Remember Arno the "head failed" message after the second get > > in my demo? This would solve it! > > As I already said, this was a good example of _missusing the component > features and is NOT a bug! > > -- > Arno Garrels -- 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
