Hi Henrik, Find my comments in line,
On 10/25/07, Henrik Plate <[EMAIL PROTECTED]> wrote: > > > Hi Ruwan, > > I was rather looking for a possibility to deal with multiple response > messages that originate from multiple send mediators in the in flow (this > is > also how I understood your original posting to which I referred). Well, For this case if you need to send the same message coming from the client to the number of services then you can use the clone mediator, which will clone the message and allows you to send the cloned messages to the number of services may be after further mediation by synapse, as described in the above configuration. Or else if you have multiple parts in the message coming from client and if you need to split those parts and use the appropriate par of the message as a new message to the service then you can use the *iterate* mediator which is very same in the configuration as clone. Let me know what exactly you want to do, so that I can help you with the exact configuration. The aim is that (1) a client sends a request to a Synapse proxy which (2) > uses multiple send mediators to forward the request to a series of > services, > each having the authority to send a reply. The Synapse proxy should then > (3) > evaluates and collects these response messages (or drops some of them) > before sending them all together to the requester. Of course, the latter > probably requires my own Mediator class. Cool, I am in the process of writing an aggregate mediator which implements the Aggregator EIP and will be able to handle this scenario. I was designed this aggregate mediator and clone/iterate mediators exactly to support your requirements. :) Give me some time to finish that up, so that you will only have to write the aggregation algorithm. One problem seems to be related to your remark about the HTTP connection: > The different response messages all run separately through the out flow (I > imagine). Here, I would need a means to collect a response message for > later > processing/sending/evaluation, hereby keeping the HTTP connection open. I have already handled this problem and addressed this issue in the above described mediator Thanks, Ruwan Any idea? > > Thank you, > Henrik > -- > View this message in context: > http://www.nabble.com/Multiple-responses-tf4651525.html#a13406829 > Sent from the Synapse - Dev mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Ruwan Linton http://www.wso2.org - "Oxygenating the Web Services Platform"
