Re: [Dev] Dev studio expands

2018-01-11 Thread Kevin Ratnasekera
Seems I missed the correct PR. [1] [1] https://github.com/wso2/wso2-synapse/pull/265 Regards Kevin On Fri, Jan 12, 2018 at 12:03 PM, Kevin Ratnasekera wrote: > Hi Lahiru, > > Yes, the statement you pointed out is no longer a valid statement. We need > to correct the

Re: [Dev] Dev studio expands

2018-01-11 Thread Kevin Ratnasekera
Hi Lahiru, Yes, the statement you pointed out is no longer a valid statement. We need to correct the documentation. [1] Thanks for pointing out. [1] https://github.com/wso2/wso2-synapse/pull/265 Regards Kevin On Thu, Jan 11, 2018 at 10:03 PM, Lahiru Sandaruwan wrote: > Hi

Re: [Dev] Dev studio expands

2018-01-11 Thread Lahiru Sandaruwan
Hi Kevin, Thanks for the response. [1] says below about 'Maximum Concurrent Accesses', "When this parameter is used, the same Throttle mediator ID should be included in the response flow so that the completed responses are deducted from the available limit." Do we need to update docs? [1]

Re: [Dev] Dev studio expands

2018-01-05 Thread Kevin Ratnasekera
Hi Lahiru, As far as I can remember, you no longer need to have empty throttle mediator tag in OUT sequence, with same throttle id as in IN sequence. This empty throttle mediator tag served purpose of decrementing concurrency throttling counter ( number or parallel flows ) which was incremented

[Dev] Dev studio expands

2017-12-21 Thread Lahiru Sandaruwan
Hi, As per [1], when throttling mediator is used in out sequence, it should be one liner, such as . But when we save that in Developer studio, it expands to following, Looks like a bug. Could we fix? [1]