Rupert Smith wrote:
So is the plan to move JMS support onto pure 0-9, then revert 0-8 support to
be pure too for interop with other 0-8 brokers? Or will JMS continue to run
over impure 0-8, with purity restored through the STRICT_AMQP flag?

I haven't kept up with the M2.1 branch and the multi-version support, but previously the STRICT_AMQP flag has not itself restored 'purity', it has merely prevented some additional methods etc being used. In particular it never restored the correct definition of the basic.consume method.

Note that the modifications to the specification file mean that the c++ client and broker are also 'impure'. If we revert to a clean spec file the c++ code will need minor adjustments before it will compile.

Reply via email to