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