Hi, > Note that the "single" concurrency just throws an error if you try to > invoke a second call while there is another one in progress for the > same RemoteObject. I thought it queued up the request (it's has been a while since I've used it in anger). I've checked the docs and yes it seems the calls will fail right away if you make another call - although I've not tested this.
Perhaps we need to add concurrency="queued" or equiv to RemoteObject? Thanks, Justin