The docs [1] indicate that the client is "a very lightweight wrapper around AmqpNetLite." If that is the case why is it advertised as the "ActiveMQ Artemis Client for .NET"? Couldn't it be used for *any* AMQP 1.0 use-case? How is it different from AmqpNetLite? What specifically does the wrapper provide?
Generally speaking, one of the nice things about implementing standardized protocols in the broker is that anybody can implement clients and those clients exist completely independent of the broker. There are *lots* of clients for STOMP, AMQP, and MQTT written in lots of different languages for all kinds of different platforms. If we cited your client in the documentation then someone could logically ask why we don't also cite client X in the documentation as well. Clients come and go over time and in my opinion it would kind of be a drag to develop and maintain a list of these clients. Justin [1] https://havret.github.io/dotnet-activemq-artemis-client/ On Wed, Feb 3, 2021 at 3:21 PM Havret <h4v...@gmail.com> wrote: > Hi Guys, > > I have been working for over a year now on unofficial ActiveMQ Artemis > Client for .NET, and a set of extension libraries that make its integration > with .ASP.NET <http://asp.net/> Core projects as seamless as possible. > Recently I have written an article describing how to use it on my blog. Do > you think there is any space in Artemis docs to include it, so it would be > easier for .NET folks who are thinking about using Artemis to find it? > > I've reached Clebert in the first place, and he suggested sharing this > here. > > I am sending you links so you could check it out: > article: https://havret.io/activemq-artemis-net-core > repository: https://github.com/Havret/dotnet-activemq-artemis-client > extensions: https://github.com/Havret/activemq-artemis-extensions > docs: https://havret.github.io/dotnet-activemq-artemis-client/ > > Thanks, > Krzysztof >
