Right now it doesn’t support
singleton access. Generally if you need to ensure a singleton you write a
simple adapter object that can be instantiated and will proxy logic through the
singleton. Even if method A returns void you can
still use the result event to indicate when it has completed (event.result may
just be null). Matt From: Thanks Matt On 10/11/05, Matt
Chotin <[EMAIL PROTECTED]>
wrote: 1. Multiple means that multiple calls to the same method are
allowed before previous calls have returned. This is the default behavior
and what you're generally used to when calling any method. We added a few
more concurrency values to try to simplify logic if you really didn't want to
think about the case of "what happens if someone sends again before the
first call returned." "single" means that once a call has
gone out no other calls to the same method (off the same RemoteObject instance)
are allowed until the first call returns. Therefore you are guaranteed
that the result event will only fire for that first call.
"last" is the opposite, if you call the method multiple times in a
row only the last call will have its result returned in the result event.
However, all calls will make their way to the server, it's just the previous
calls results or faults will be ignored. This is mentioned somewhere in
the docs I'm sure, just search for "concurrency" 2. Call remote object A, in the result handler for A call
method B using the return values from A. Matt From: flexcoders@yahoogroups.com
[mailto:flexcoders@yahoogroups.com]
On Behalf Of Aly Sidi quicl question about mx:method concurrency. -- YAHOO!
GROUPS LINKS
|
- RE: [flexcoders] mx:method Matt Chotin
- [flexcoders] Re: mx:method Dave Wolf