On Thu, 2017-02-09 at 15:30 +0000, Gordon Sim 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.
Gah, I had not realized that the SWIG client was not a drop-in replacement even aside from protocol differences. If it was just the URL format, we could easily have the SWIG client use the python URL parser instead of the C++ one, but if there are more differences (SASL config??) then it is not simple at all. Can you make a list of all the things that differ between the clients so we can figure out how to deal with this? It doesn't sounds as simple as a command line flag for AMQP 1.0 if you need to replace your SASL configuration as well just to change the protocol the management client speaks. > > --------------------------------------------------------------------- > 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]
