On Fri, 2017-02-10 at 07:32 -0800, Justin Ross wrote: > Tracked in https://issues.apache.org/jira/browse/QPID-7669 >
I think we decided that making the command line tools do AMQP 1.0 wasn't solving the real problem anyway (need a proton-based mgmt library) so perhaps we should revertt QPID-7432. From Gordon's comments the swigged python client is not even remotely a drop-in replacement so it was a bad idea to make it the default (or use it at all) in any of our management clients. > On Thu, Feb 9, 2017 at 7:30 AM, Gordon Sim <[email protected]> wrote: > > > On 09/02/17 15:20, Gordon Sim wrote: > > > > > It seems that the swigged c++ implementation is now prefered to > > > the pure > > > python on. Not sure why that was done; I hadn't even realised it > > > had > > > been done. > > > > > > > This was done as the fix for https://issues.apache.org/jira > > /browse/QPID-7432, i.e. in order to allow management tools to work > > over > > AMQP 1.0. > > > > However, it does not take into account some differences between the > > c++ > > and python implementations, particularly for SSL configuration. > > > > It would be nice to make the preference for the swigged version > > somehow > > conditional. E.g. through a command line option that specifically > > requests > > AMQP 1.0. > > > > > > ----------------------------------------------------------------- > > ---- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
