SOAPEncoder throws an exception, which is caught by Operation, swallowed, and then a fault event is dispatched from the Operation instance. If you do all your async stuff using responders because you need to know *which* action has just finished or faulted (among other things), you never get to hear about it.
-Josh On Fri, Dec 12, 2008 at 2:20 PM, Mark Carter <[email protected]> wrote: > > > Josh McDonald-4 wrote: > > > > The problem is that from the SDK's point of view, there is no request. > > There's no IMessage, there's nothing to wait on. However from the > > application's point of view, there is. > > > > I don't quite understand... > > Wouldn't any problems before the async token is returned, be thrown as an > exception from the method returning the async token? Therefore the calling > code just needs to catch that exception and handle it. > > The only problem with this would be if an event is generated after the > async > token is returned and before the responder is added. This would only be an > issue in a multi-threaded environment. > > > -- > View this message in context: > http://www.nabble.com/Best-practice-for-calling-asynchronous-functions--tp20930596p20969714.html > Sent from the FlexCoders mailing list archive at Nabble.com. > > > ------------------------------------ > > -- > Flexcoders Mailing List > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > Alternative FAQ location: > https://share.acrobat.com/adc/document.do?docid=942dbdc8-e469-446f-b4cf-1e62079f6847 > Search Archives: > http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups > Links > > > > -- "Therefore, send not to know For whom the bell tolls. It tolls for thee." Like the cut of my jib? Check out my Flex blog! :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [email protected] :: http://flex.joshmcdonald.info/ :: http://twitter.com/sophistifunk
