@Clebert
So the idea is to reduce the impedance mismatch between Artemis address
model (which is geat!) and the concepts from jms/nms (not so great, at
least 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 its
address, routing type (Multicast, Anycast) and queue name. It would be nice
if I could define if the subscription is shared and durable as well. If
this particular queue doesn't exist, currently the exception is thrown. I
would like to change this behavior, to create the queue dynamically. The
same way as queues are created for jms 2.0 subscriptions. Sample api would
look like this
var consumer = await connection.CreateConsumerAsync("test-consumer",
RoutingType.Anycast, "q1");
@Justin
I'm using AMQP. The very early POC is here
https://github.com/Havret/ActiveMQ.Net
On 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?
> >
>
