> My inclination would be to add some sort of policy or mode to messenger.
> I'm not sure what I'd call it, but with this mode enabled, messenger (when
> started) would always maintain active connections and/or links to any
> declared routes. I think this is a bit more flexible than just the ability
> to test a connection because a route can include the node information as
> well. This would, e.g. give you the option of failing fast not only if the
> broker was down, but also if the queue doesn't exist. In the python
> binding
> it would look something like this:
>
> messenger.blah_mode = True
> messenger.route("broker1/*", "broker1.foo.com/$1")
> messenger.route("queueA", "broker2.bar.com/queueA")
> messenger.start() # this would now blow up if broker1 or broker2 is
> inaccessable, or if queueA doesn't exist.
>
> Does this seem like it would cover your use case?
That sounds like a good solution and would certainly meet our needs.
Should we raise a New Feature issue in JIRA to track and discuss this
further?
That way you can have a think about how you'd prefer to see it implemented,
and
in the mean time we can put together a small patch toward this general idea
and
either submit that on JIRA, or allow you to come up with your own and we can
rebase our API on top of that later.
--
Dominic Evans
WebSphere MQ - Development
IBM Software Group, Hursley Park, UK
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Using-the-messenger-API-to-connect-to-a-server-without-sending-or-subscribing-tp7607184p7607280.html
Sent from the Apache Qpid Proton mailing list archive at Nabble.com.
