On 07/09/2015 03:25 PM, Jan Rinze wrote:
What's the equivalent of the JMS mandatory_topic flag in C++?
Sending a message to an direct exchange that has no alternative exchange
setup and no binding for the specified key will always silently drop the
message. There seems to be no documentation on
On 07/09/2015 09:03 PM, dylan25 wrote:
Hello,
I'm currently incorporating SASL authentication functionality into my
messaging client, and testing it with RabbitMQ (using the AMQP 1.0 plugin).
I am formatting my URIs as follows using this scheme:
amqp://user:pass@127.0.0.1:5672/exchange/topic. I
On 07/11/2015 05:52 PM, Fraser Adams wrote:
On point b. has anyone (most likely Gordon) explored the scaling limits
of qpidd? Obviously when Qpid started out servers tended to have
something between one and four cores, but now of course Moore's law
tends to be followed by increasing the number
On 11 July 2015 at 17:52, Fraser Adams fraser.ad...@blueyonder.co.uk wrote:
Hey all,
Suppose I have a queue on qpidd, I know that I can have multiple consumer
clients subscribing to that queue node - I've used that several times to
provide a means of scaling out consumers, so if I have n
I was using Proton 0.9, although I was able to get SASL to work when I
switched to 0.9.1-rc1. Thank you for your help, Gordon!
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Using-Proton-Messenger-with-SASL-tp7627962p7628105.html
Sent from the Apache Qpid users mailing list
On Sun, 2015-07-12 at 09:14 +0100, Fraser Adams wrote:
As I say I think that ActiveMQ Apollo started out because of scaling
limitations of the original ActiveMQ and has evolved to a reactor
based
threading model built on hawt-dispatch (Java implementation of Grand
Central Dispatch
