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.
