Re: [flexcoders] concurrency=last

2005-12-01 Thread Rich Tretola
@yahoogroups.com] On Behalf Of Rich Tretola Sent: Wednesday, November 30, 2005 4:25 AM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] concurrency=last Matt, They are 4 different methods being called on the same service. Rich On 11/30/05, Matt Chotin [EMAIL PROTECTED] wrote: I

Re: [flexcoders] concurrency=last

2005-11-30 Thread Rich Tretola
@yahoogroups.com] On Behalf Of Ben Lucyk Sent: Tuesday, November 29, 2005 8:16 AM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] concurrency=last Hey Rich, I haven't tested, but looks to be that concurrency is set per service: Value that indicates how to handle

RE: [flexcoders] concurrency=last

2005-11-30 Thread Matt Chotin
. Matt From: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] On Behalf Of Rich Tretola Sent: Wednesday, November 30, 2005 4:25 AM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] concurrency=last Matt, They are 4 different methods being called on the same

Re: [flexcoders] concurrency=last

2005-11-29 Thread 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

RE: [flexcoders] concurrency=last

2005-11-29 Thread Matt Chotin
] concurrency=last 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