This is why I don't advocate use of the AsyncCommand utility in these forums. It seemed as if it would be a good idea but the demo uses timers. Although it's asynchronous, it doesn't represent this scenario well, when a proxy becomes involved. You have to pass it a reference to the AsyncCommand's onComplete function, because the running command can't subscribe to notifications
I personally use the StateMachine Utility
1 to split my application's runtime into discrete States. This is a great way to handle async activity.
-=Cliff>
1StateMachine Overview:
http://puremvc.tv/#P003