RHEL is pushing Dispatcher + Broker-J (Artemis based) as the new A-MQ
solution.
With container and another new things happening, could be the new way.
But C++ broker still the fastest and best broker around for me
On Fri, Mar 6, 2020 at 1:33 PM Robbie Gemmell
wrote:
> The C++ broker sees occasio
Hi Olivier
I'm not entirely sure what your exact idea here is - are you looking to
have Broker-J trigger the deletion on the blob at the point at which it
believes it no longer needs the message? Or maybe to update the blob store
to make clear that the broker no longer needs to retain a copy of t
The C++ broker sees occasional bug fixes (some are probably overdue a
release currently, its been a while), but there isnt active feature
development around it.
On Fri, 6 Mar 2020 at 15:39, Bruce Parr wrote:
>
> Hello,
>
> Is the C++ broker still under development/maintenance, or should we start
Hello,
Is the C++ broker still under development/maintenance, or should we start
thinking about switching to Broker-J?
Thanks,
Bruce
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mai
Hello,
We're trying to implement the claim-check pattern on top of our broker +
dispatch-router topology.
So we have a blob store and the idea is for each message above 10KB to store
the payload in it and to only keep an ID in the message.
The tricky part is the delete of the payload in the blob
