Here is how I do this: 1) create a single result handler function, used by all calls.
2) When I invoke send, on the returned AsyncToken, I set a property, "sCallId", to a string that identifies the call 3) When a result returns, I get the "sCallId" and use it in a switch statement to run the appropriate processing, often another data service call. This is very easy to set up and to maintain. The key is the AsyncToken returned by send(). Tracy ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Karl Johnson Sent: Monday, February 26, 2007 11:03 AM To: [email protected] Subject: RE: [flexcoders] Looking for guidance on HTTPService sequencing Data access via HTTP and Web services is asynchronous so there is no way to guarantee natively that your services return in a certain order. But you can accomplish this if you really need to by chaining together service calls via result handlers. Calling service 1, and then in the result handler for service one, calling service two, and so on. Karl Cynergy From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of pgp.coppens Sent: Monday, February 26, 2007 9:28 AM To: [email protected] Subject: [flexcoders] Looking for guidance on HTTPService sequencing Hello Flex fans, Yet another flex 101.... I have read and (hopefully) understood how HTTPService and its result handling works. What I am struggling with is how I can enforce a certain sequencing so that I have the guarantee that flash will not send a second request after the first has been completed. Alternatively, are there any synchronization mechanisms available at all that could be used to implement the above? Thanks, Peter
