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 ?
Here is the situation (Flex 1.5):
I have a piece of data in my model that when changed will fire off 4 method calls using the same service (Remote object call to java) with concurrency="last". It seems that I never get all 4 responding and that the concurrency is per service id ? Am I correct in this ? I always assumed that the concurrency set to last would be last call to a specific methd to avoid double calls to a specific method and not a specific service.
Rich
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
YAHOO! GROUPS LINKS
- Visit your group "flexcoders" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
YAHOO! GROUPS LINKS
- Visit your group "flexcoders" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
