Hey Gordon, Thanks, much clearer now :)
>> I think/thought "properties" is different from "application-properties", > > The 'properties' field on the proton Message object is exclusively > mapped to application-properties in the amqp message encoding. OK, thanks very much for assuring that. > I agree the naming there is confusing! Yup. Glad I asked :) Glad you helped out! > Yes, but the library should handle the appropriate conversion there. OK, fine with me. I do care about the protocol on the wire, for reasons of compatibility and wanting to do it right. Code is married to a library so it may be locally tweaked :) >> This is typical for "symbol", one from a limited set of values, but I am >> looking to cover "string", which I expect in application-properties. > > Not sure I understand your concern here completely. The key and value > can be any arbitrary utf8 string. The value can also be a number if > preferred. As I understand it (but that's from the spec), the strings may not have arbitrary values but must come from a restricted set. Like an enumerated type, basically. If the actual implementation just allows any string _and_ behaves like it on the wire, then I'm satisfied. It is, once again, a bit confusing (only did one small tool on Proton before, you may have guessed my laymanship). Thanks for clearing this up! -Rick --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
