Still not sure to understand, sorry. What is the added feature compared to the routing slip EIP pattern [1] ?
This component already handle the asynchronous reliable InOut patterns, but yes, it needs a store to keep the original exchange. Do you just want to get rid of the store ? I guess we just need to send the original exchange along with the requests to services (as a property on the exchange). I think the performances may be better if a few services are used, else it may be more costly as the original exchange will be serialized for each exchange instead of only once. [1] http://servicemix.goopen.org/site/servicemix-eip.html#servicemix-eip-StaticRoutingSlip On 10/2/06, Jamie McCrindle <[EMAIL PROTECTED]> wrote:
hiya, > Could you be a bit more precise about your > wrapping / unwrapping operation ? one way to do this would be with a message history pattern. have a stack of ME's as an exchange property and just pop them as the in-out's come back through the pipeline. of course, that'd be hideously inefficient after a few hops. the stack could be smarter and just store delta's (that'd probably be useful for just doing the message history pattern too). if each component in the pipeline is changing the content radically then there still wouldn't be that much benefit but often intermediate components are doing aop-like things like logging, authentication, caching which don't actually touch the contents particularly much (of course, all of the previously mentioned use cases are catered for in other ways by servicemix but you get the idea). please let me know if you need more info. cheers, j. On 10/2/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote: > Could you be a bit more precise about your > wrapping / unwrapping operation ? > > On 9/29/06, Jamie McCrindle <[EMAIL PROTECTED]> wrote: > > Hi, > > > > Not sure if this makes sense but: > > > > I'd like a way to do reliable / clustered / asynchronous in-out > > pipelining of message exchanges without having to use a JdbcStore. One > > way to do it would be to able to wrap message exchanges as they pass > > through each component in the pipeline (and then unwrap them on the > > way back). > > > > cheers, > > j. > > > > On 9/29/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote: > > > ServiceMix is ultimately your project, and we need feedback > > > to help focus on what you think is needed to improve the project. > > > > > > If you have ever thought, "ServiceMix would be such a nice project, if > > > only ...", > > > it' s time to speak ! > > > > > > We'd like to hear from everyone, from beginners to advanced users, > > > so please fell free to speak and list the topics you'd like to > > > improve or new features to be implemented. > > > > > > Please, every user out there, give us your top 5 things we > > > can do to make ServiceMix better for you. > > > > > > -- > > > Cheers, > > > Guillaume Nodet > > > > > > > > -- > Cheers, > Guillaume Nodet >
-- Cheers, Guillaume Nodet
