Yes, you are right. And as one of the authors of this implementation, I share your feelings. That's why I started experimenting with something more .NET friendly. The idea is to create fully asynchronous ActiveMQ (Artemis) .NET client without all these NMS/JMS constraints and baggage. Sth like we have for RabbitMQ.
On the other hand, however, NMS/JMS is a proven concept that should live up to most of your expectations. If you want sth fully customizable you can try to use AmqpNetLite directly On Sun, Dec 29, 2019 at 8:42 AM dotnetuser <[email protected]> wrote: > It seems to me that the current implementation has a big problem with > extensibility without changing internal methods. NMS is an AQMP wrapper. > Moreover, almost all native methods are asynchronous inside, but this is > not > in the wrapper, which is not very convenient for the dotnet environment. > > > > -- > Sent from: > http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html >
