I'm doing some interop work on the go binding, and I see something strange in the 'message.amqp' file in tests/interop. The message body is encoded as:
0x77, 0xa0, 0x7, 0xa1, 0x5, 0x68, 0x65, 0x6c, 0x6c, 0x6f ^ AMQP value section ^Binary ^7 bytes ^String ^5 bytes h e l l o In other words there's an AMQP-encoded string *inside* an AMQP encoded binary. Looking at the python code that generated this message I would expect it to be an AMQP 5 byte binary value "hello". I think the intent was for it to be a string, but in python plain "hello" is binary you need to say u"hello" to get a string. However I can't see any reason why there would be a string *inside* a binary. Anyone have a clue what's going on here? Cheers, Alan.