Thanks. That closes this issue. BTW, I read in the following article that a callback closure code which is invoked to process the result of an Async API will actually execute on the context of the main GUI thread.
http://ria.dzone.com/category/tags/adobe-flex-air-ria-async-asyn Is this documented somewhere within the SDK? --- In [email protected], Gordon Smith <gosm...@...> wrote: > > You can assume that anything not documented as being asynchronous is > synchronous. > > Gordon Smith > Adobe Flex SDK Team > > From: [email protected] [mailto:[email protected]] On > Behalf Of itaid1 > Sent: Friday, May 14, 2010 9:35 AM > To: [email protected] > Subject: [flexcoders] Re: Flex Events > > > > > --- In [email protected]<mailto:flexcoders%40yahoogroups.com>, Oleg > Sivokon <olegsivokon@> wrote: > > > > dispatchEvent is a regular method and it id executed synchronously. If you > > call it twice, then the same group of listeners will be called twice in the > > same call stack. If you want to manage the order in which handlers are > > called you can specify priority when adding them, however, if you must add > > many handlers (many would be hundreds) I would rethink using priority as the > > handlers are sorted when added and the more handlers there are with the > > certain priority specified, the slower the adding will be. > > > Thanks! Did you figure it's synchronous aspect through testing or is this > documented somewhere? >
