Comments on: Extending ActionScript classes to provide AsyncToken like behavior http://corlan.org/2008/08/11/extending-actionscript-classes-to-provide-asynctoken-like-behavior/?utm_source=rss&utm_medium=rss&utm_campaign=extending-actionscript-classes-to-provide-asynctoken-like-behavior Flex, AIR and Rock&Roll Thu, 09 Sep 2010 00:42:32 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: sydd http://corlan.org/2008/08/11/extending-actionscript-classes-to-provide-asynctoken-like-behavior/comment-page-1/#comment-1579 sydd Tue, 13 Jan 2009 17:48:34 +0000 http://corlan.org/2008/08/11/extending-actionscript-classes-to-provide-asynctoken-like-behavior/#comment-1579 great article, many thanks for it :) great article, many thanks for it :)

]]> By: Mihai Corlan http://corlan.org/2008/08/11/extending-actionscript-classes-to-provide-asynctoken-like-behavior/comment-page-1/#comment-769 Mihai Corlan Mon, 11 Aug 2008 15:01:23 +0000 http://corlan.org/2008/08/11/extending-actionscript-classes-to-provide-asynctoken-like-behavior/#comment-769 @Rob McKeown Good point. Indeed, I would have a problem in this case. So, the way you should use MyLoader for multiple calls is to instantiate for each call if you plan to do multiple calls one after another. @Rob McKeown

Good point.
Indeed, I would have a problem in this case. So, the way you should use MyLoader for multiple calls is to instantiate for each call if you plan to do multiple calls one after another.

]]> By: Rob McKeown http://corlan.org/2008/08/11/extending-actionscript-classes-to-provide-asynctoken-like-behavior/comment-page-1/#comment-768 Rob McKeown Mon, 11 Aug 2008 14:29:18 +0000 http://corlan.org/2008/08/11/extending-actionscript-classes-to-provide-asynctoken-like-behavior/#comment-768 Wouldn't you have a problem if you used the same loader to make more than one async call given that it is possible that a second request could be sent before the first response comes back? Since the token is just being stored in the loader, any subsequent call would overwrite the previous value making it impossible to "link" the data to its request. I think the AsyncToken in flex does not have that issue. Wouldn’t you have a problem if you used the same loader to make more than one async call given that it is possible that a second request could be sent before the first response comes back? Since the token is just being stored in the loader, any subsequent call would overwrite the previous value making it impossible to “link” the data to its request.

I think the AsyncToken in flex does not have that issue.

]]>