Thanks for the clarification
I have left comments on the PR.
PLAT.
Thanks,
Penghui
On Sat, May 7, 2022 at 9:56 PM Enrico Olivelli wrote:
> Peng Hui
>
> Il giorno ven 6 mag 2022 alle ore 12:54 PengHui Li
> ha scritto:
> >
> > > The problem is that If I use multiple subscriptions then I am not
Peng Hui
Il giorno ven 6 mag 2022 alle ore 12:54 PengHui Li
ha scritto:
>
> > The problem is that If I use multiple subscriptions then I am not
> guaranteed that each message is delivered only to one consumer.
>
> It is a weird use case, but it is something that is possible according
> to the JMS
Lin Lin
Il giorno ven 6 mag 2022 alle ore 16:51 Lin Lin ha scritto:
>
> The addition of this feature looks like a matter of consumer selection.
> Should the consumer selection of each Dispatcher be abstracted into an
> extensible interface?
This would be useful and a great addition, but actuall
The addition of this feature looks like a matter of consumer selection.
Should the consumer selection of each Dispatcher be abstracted into an
extensible interface?
Thanks
Lin Lin
> The problem is that If I use multiple subscriptions then I am not
guaranteed that each message is delivered only to one consumer.
It is a weird use case, but it is something that is possible according
to the JMS specs.
I am mapping a JMS Queue with a Subscription, and everything works well,
but
It looks like we can add something like `EntryDispatcher` before the
EntryFilter.
Mixing entry filtering and consumer selecting seems a little confusing.
The `EntryDispatcher` could works as a consumer selector in
`PersistentDispatcherMultipleConsumers`.
It accepts an entry and a consumer li
Il giorno ven 6 mag 2022 alle ore 01:50 PengHui Li
ha scritto:
>
> > The Message goes through the EntryFilter that decides if the Entry
> matches the requirements of the Consumer.
> - if the message matches the consumer then it returns ACCEPT
> - if the message does not match the consumer then it
> The Message goes through the EntryFilter that decides if the Entry
matches the requirements of the Consumer.
- if the message matches the consumer then it returns ACCEPT
- if the message does not match the consumer then it has to be
rescheduled (RESCHEDULE)
It looks like different consumers have
Hello,
I am trying to use PIP-105 and I found out that we are missing a few
little things to cover my user case.
In my case I have two consumers who compete on the same SHARED
subscription with a "message filter".
The filter is passed as Consumer metadata.
When you have two Consumers connected on
