On 07/21/2014 04:56 PM, Alan Conway wrote:
On Mon, 2014-07-21 at 13:16 +0100, Gordon Sim wrote:
On 07/21/2014 01:12 PM, Andreas Welchlin wrote:
Funny that it seemed to work with "decode()" as long as I only used C++
applications. I think the reason was that the C++ senders used also
"encode()".
Yes, that would result in an AMQP 0-10 encoded map (with the content
being 'binary' as far as AMQP 1.0 is concerned).
Given that we have multiple incompatible ways to extract data from a
message, is it possible to detect incorrect use and raise an exception
rather than just returning nothing?
In this case an exception was raised. The associated message could
certainly be more obvious though, e.g. 'decoding of AMQP 0-10 map
failed' perhaps.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
