You're right. Both NMS and CMS are APIs + implementations. That's a fair point.
However, the only two implementations for both which have releases in the last 9 years are OpenWire and STOMP, and the STOMP providers have limitations as compared to the OpenWire ones. It's not clear to me that "its very easy to switch over" to AMQP as there has been no AMQP provider released for NMS or CMS. There is no AMQP provider for CMS whatsoever. Initial work on an AMQP provider for NMS was done back in 2014 [1] and then a "rework" to wrap Amqp.Net Lite[2] was proposed in early 2017 [3]. That work was completed over the first half of 2018 [4]. But there's still been no release. With both the initial work and the rework it appears that the original developers abandoned it and there was no one else to pick it up. In my opinion this illustrates my point about these projects not really having a community. Justin [1] https://issues.apache.org/jira/browse/AMQNET-454 [2] http://azure.github.io/amqpnetlite/ [3] http://activemq.2283324.n4.nabble.com/DISCUSS-Rework-NMS-AMQP-tp4721986.html [4] https://issues.apache.org/jira/browse/AMQNET-575 On Thu, Mar 7, 2019 at 2:04 PM <[email protected]> wrote: > So the point of these is they provide a clean api regardless of underlying > protocol. > > > > > Its not based on openwire so i disagree on your point there, it is > providing a higher level api abstraction. Which open wire is just one of > many protocols implementing the api. > > > > > E.g. amqp switch over from open wire here are clear points for a developer > to switch from one to the other, as there is an implementation for both > against nms, its very easy to switch over. > > > > > > > > > >
