|
I believe concurrency should be done on an
operation basis but the setting is inherited from the service you don’t
assign one. The default is multiple. Are you making 4 different method calls or
4 calls to the same method? If the same method then obviously a setting of last
should only return 1 instead of all of them, but if they’re different
methods that would sound like a bug. Matt From: [email protected]
[mailto:[EMAIL PROTECTED] On Behalf
Of Ben Lucyk Hey Rich, I haven't tested, but looks to be that concurrency is set per service: "Value that indicates how to handle multiple calls to the same
service. The default value is multiple. The following values are
permitted..." I guess you could work around it by defining a service for each method
if you really needed this functionality, but I'm curious about this one as
well. Does anyone have any more details as to how Flex "...cancels
any previous requests, while honoring the new one" for a concurrency="last"
situation? -Ben On 11/29/05, Rich
Tretola <[EMAIL PROTECTED]
> wrote: Does the service
concurrency work on a per method basis or per service ? YAHOO!
GROUPS LINKS
|
- RE: [flexcoders] concurrency="last" Matt Chotin
- Re: [flexcoders] concurrency="last" Rich Tretola
- RE: [flexcoders] concurrency="last" Matt Chotin
- Re: [flexcoders] concurrency="last" Rich Tretola

