Good find! There certainly is a way (probably multiple ways) to avoid this, and I’ve updated the example to handle a rapid double-click. If you download the example again, look to make sure the explorer.as has the date of Jan 3, 2004 (just to be sure the archive isn’t getting pulled from your browser cache).

In the update I’ve added blocking such that only the first click (request) is handled. I accomplished this by setting a boolean flag in the method that is called when a node is opened. Subsequent node expansion (requests) will simply be ignored until the initial service result (response) has be recieved and the values have been displayed. Clearing the flag is managed through the service result method (in this case the directories() method).

Ideally there’d be message queueing in the Flex application on the client, but I suspect that would involve some intelligence on the server as well (remoting runtime service). For now, mine is quick and easy. We’ll see what the future brings.

1. Click on a node.
2. Before the children of that node are displayed click on another node (you have do this really fast :). Prmoinent result when you are accessing web services over the net!)

The result would be that the children of the previous node (fist click) will be displayed as children of the subsequently clicked node.

Is there any way we can avoid this.!