KPShared durable and shared non durable is covered in JMS 2.0 api. The NMS api 
is meant to be a JMS equiv. As such simply we need to add those methods and 
other parts of JMS 2.0 to NMSNo need to make new or different apis IMHOMikeSent 
from my Samsung Galaxy smartphone.
-------- Original message --------From: Krzysztof <h4v...@gmail.com> Date: 
09/01/2020  22:05  (GMT+00:00) To: dev@activemq.apache.org Subject: Re: 
Artemis: AMQP create queue based on FQQN @ClebertSo the idea is to reduce the 
impedance mismatch between Artemis addressmodel (which is geat!) and the 
concepts from jms/nms (not so great, atleast for folks from .net world, who 
used to work with rabbit mq before).I would like to be able to create a 
consumer and attach it by defining itsaddress, routing type (Multicast, 
Anycast) and queue name. It would be niceif I could define if the subscription 
is shared and durable as well. Ifthis particular queue doesn't exist, currently 
the exception is thrown. Iwould like to change this behavior, to create the 
queue dynamically. Thesame way as queues are created for jms 2.0 subscriptions. 
Sample api wouldlook like thisvar consumer = await 
connection.CreateConsumerAsync("test-consumer",RoutingType.Anycast, 
"q1");@JustinI'm using AMQP. The very early POC is 
herehttps://github.com/Havret/ActiveMQ.NetOn Thu, Jan 9, 2020 at 3:16 AM Justin 
Bertram <jbert...@apache.org> wrote:> What protocol is the client going to 
use?>>> Justin>> On Sun, Dec 29, 2019 at 3:53 PM Krzysztof <h4v...@gmail.com> 
wrote:>> > I'm just wondering if it should be possible to create queue based on 
the> > value specified via FQQN. Currently you cannot attach to the queue if 
it> is> > not pre-configured.> >> > I'm working on POC of .NET ActiveMQ client 
and I am trying to give the> > potential user as flexible API as possible.> >> 
> The draft API assumes that it should be feasible to specify address,> > 
routing type (Multicast, Anycast), queue name, durability, and whether> the> > 
queue should be shared or not.> >> > This way user would be able to leverage 
most of the Artemis Address Model> > configuration options directly from the 
code without pre-configuration> > anything on the broker side.> >> > What do 
you think?> >>

Reply via email to