On 2 March 2011 07:58, Charles Moulliard <[email protected]> wrote: > Hi, > > Regarding to the new name of NMR, we could use another acronym --> SML > = ServiceMix Messaging Layer or EML = Endpoints Messaging Layer as the > main goal of this component will be to deliver messages to endpoints > exposed in bundles or in another SMX instances, will also handle > transaction between transactional endpoints, audit messages, provide a > registry to locate endpoints registered and least but not least > provide clustering or clouding
The term NMR has always been a bit confusing as it talks about Routing (which then makes folks compare it directly to Camel and then get confused as the NMR doesn't really do that much routing - it does as much routing as blueprint does with the dynamic proxies to 0....n service implementations in the OSGi registry for example). So how about calling it ServiceMix Registry? For me the big win and value of the NMR is its a universal (cross-classloader & bundle) registry of logical messaging endpoints that can use any technology underneath (ActiveMQ / Camel / CXF / ODE / OpenEJB etc). It then more clearly defines the value add ServiceMix brings above and beyond Camel; particularly as ServiceMix Registry could easily be a distributed (rather than purely in-VM only) registry of endpoints. -- James ------- FuseSource Email: [email protected] Web: http://fusesource.com Twitter: jstrachan Blog: http://macstrac.blogspot.com/ Open Source Integration
