Hi, The event handler function is already in a mesage posted by triggerrequestdone. I think the problem is not "too less" messages but instead "too much" of it. (SetReady also posts message!) Don't you think we need a mechanism for assuring that Setready and onrequestdone is called just once per request? Or ae there exceptions?
Regards, SZ On 5/13/09, Francois Piette <francois.pie...@skynet.be> wrote: > > >I tried to provide. In the ICS Httpstst demo, which is async, I added the > > lines SslHttpCli1->GetAsync(); to onrequestdone of head and it shows > > "component not ready" error on the url I provided (68..../scripts, NOT > > www.suckersluck...). If the component is not ready in onrequestdone, when > > will it be ready?? > > When you are inside an event handler, you are still in the event processing > (the event handler is just called like a function). To be completely out of > any processing, you must use PostMessage to send a custom message. And from > the correponding handler you can do anything with the component. You are > guranteed to be out of everything. > -- > francois.pie...@overbyte.be > 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
