Dealing with asynchronous results handling.

[jff_ebt]

Thanks for the information so far.

The first response seems to be an example of chaining (i.e. results from one
service call, calls the next service) which I'm trying to avoid. If I
misunderstood, let me know.

I have looked at the "call" object and that may be helpful. Acutally the Flex
manuals mention this in combination with the ACT (Asynchronous Completion
Token?) pattern. That should be useful for keeping track of requests that
have completed.

One thought I had was to send in an array or tree of functions. The idea
being to load up the array with the services I want to call and the order I
want them called. Each result handler will take itself out of the array and
then call the next function in the array. When the array/tree is depleated, we
know we're done.

Haven't tried to code this up yet. Not sure if I can create create such a
array/tree in ActionScript. I'll let you know if that works out.

[ntsiii]

I use a similar strategy in some cases. Sometimes a value array will require
two or more queires be completed before it is usable.

When the query(data service send()) is invoked, I add an entry to an array
with the id of the query, and store the id in the call object. When a result
event calls the handler, I get the id of the calling request, remove the
matching element from the array. When the array is empty, the data array is
ready to be assigned to a dataProvider property.

[ntsiii]

And yes, you can actually pass a function to the call object, and run it rom the result handler. I have not tried this yet, though.