synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Fremantle" <>
Subject Re: proposed change to <send/>
Date Fri, 05 May 2006 15:55:35 GMT
I think what you are saying is exactly what I just said!

On 5/5/06, Sanjiva Weerawarana <> wrote:
> On Fri, 2006-05-05 at 14:56 +0100, Paul Fremantle wrote:
> > Well I think we need two behaviours. One is to explicitly send the
> > current message on and do no more processing (kind of like "goto
> > end"). The second is to take a copy of the message and send that
> > somewhere without affecting the current flow. However in both cases
> > the response message gets handled as a newly injected message into
> > Synapse. In the second case you have to configure Synapse to do
> > something with the extra response.
> I don't see this- if we do what I suggested (and I thought you agreed
> with earlier in this thread!), then we have <send/> basically being
> built in. However, if the built-in <send/> is reached, then the flow
> stops. If you hit an explicit <send/>, then the flow is not stopped.
> There's no "new" message created after an explicit <send/> .. the
> current message continues to get processed. (Maybe there's another
> <send/> sending it somewhere else; who knows.)
> Response has nothing to do with this discussion- if the explicit <send/>
> causes another messsage to be injected to Synapse, well, cool- but that
> has nothing to do with the current message path thru Synapse.
> Sanjiva.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair

"Oxygenating the Web Service Platform",

View raw message