I've been haphazardly following this discussion. I did some work on the NMS API last year, possibly the 20-odd commits you refer to.
It is correct to say that NMS is just a general open interface to any transport, openwire is just one. The work I did was for AMQP. I've forgotten how many transports are implemented in the NMS project but I believe it was somewhere between 3 and 6 (STOMP is there as well). Also the measure of the importance of the API should be in the downloads/use of the API, not in the code modifications. But on the other hand, if there are no tickets or bugs being raised it's probable it's not being used. The work I did to create an AMQP transport for Apache.NMS was for AMQPnetLite, not for QPID AMQP. The main thing it lacks is nuget packaging to be generally available in the .NET world. That said, I have found my priorities have changed and I'm not the person to be the champion here, so I can't argue strongly for maintaining a development tree that I won't likely contribute to very much. It would be nice to see it carried on, but if the community as a whole does not see any use for this then better to let it atrophy. Regards, Ragnar On Thu, Mar 7, 2019 at 3:58 PM <michael.andre.pea...@me.com.invalid> wrote: > I think he was wanting to make a new one that wrapping latest qpid, which > would be awesome. > > > > > Get Outlook for Android > > > > > > > > On Thu, Mar 7, 2019 at 8:48 PM +0000, <michael.andre.pea...@me.com> wrote: > > > > > > > > > > > So there is already an amqp nms implementation > > > > > Get Outlook for Android > > > > > > > > On Thu, Mar 7, 2019 at 8:08 PM +0000, "Clebert Suconic" < > clebert.suco...@gmail.com> wrote: > > > > > > > > > > > There was a guy at some point trying to implement AMQP on NMS. what > happened to that front? any knows about it? > > On Thu, Mar 7, 2019 at 3:04 PM 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. > > > > > > > > > > > > > > > > > > > > > -- > Clebert Suconic > > > > > > > > > > >
