thank you very much Gordon. >For AMQP 0-10 you can set the content-type to 'text/plain' to indicate >that it is textual data, and of course you could set that to some other >mime-type to indicate some other binary form (e.g. image/jpeg or whatever).
>In future there will be an extension to the API (already on trunk, but >won't be released until 0.26), that lets you set the content as an >object (a qpid::types::Variant). That allows the std::string to be >associated with an encoding (utf8, ascii or binary), as well as allowing >it to be a map, list, uuid or one of various numeric types. So, that means the next release (0.26, which is in trunk )already included that sending/receiving the mime type data ?? -- View this message in context: http://qpid.2158936.n2.nabble.com/How-to-test-Qpid-c-broker-tp7597435p7597451.html Sent from the Apache Qpid users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
