On 10/21/06, Paul Fremantle <[EMAIL PROTECTED]> wrote:
Oh. I imagined your point wrong. So your are talking about one synapse instance in the server side and the other synapse instance in the client side.
According to the current implementation of Sandesha2 what will matter is the destination 'To' address. So if in this scenario the destination EPR is the same, the messages will go in the same sequence. Otherwise they will go in different sequences according the the 'To' address.
Chamikara
> > But here is another nice scenario. I have two Synapses acting as
> > gateways. I just want one sequence holding them together and they
> > multiplex lots of traffic from each side over that sequence.
>
>
> In that case both synapse instances will have to work on the same shared
> Sandesha2 storage. Probably the same database.
No. Well at least thats not what I'm imagining. The idea was that
maybe one Synapse instance is Dell's gateway and the other Intel's.
They are bridging between two internal networks (maybe two JMS
networks) and lots of internal applications, but they only need one
sequence between them. They are in separate companies, so they
certainly don't share the same database.
Oh. I imagined your point wrong. So your are talking about one synapse instance in the server side and the other synapse instance in the client side.
According to the current implementation of Sandesha2 what will matter is the destination 'To' address. So if in this scenario the destination EPR is the same, the messages will go in the same sequence. Otherwise they will go in different sequences according the the 'To' address.
Chamikara
