On Thu, Sep 19, 2013 at 12:59:17PM -0400, Darryl L. Pierce wrote: > I modified the spout.pl example to do this for both the name and value > on properties pass in at the command line and they were seen by the Java > drain tool (yay!). > > So, narrowing down the goal slightly, WRT QPID-5067, do we want to 1) > require the users to explicitly called utf8::upgrade() on the property > name and value and assume that, whatever they pass in is correct, or do we > 2) assume it for them and upgrade the string in our porcelain layer? > > In this case, since message properties are always strings, the latter > seems to me to be the right path.
Okay, so with clarification from Gordon that the property name is always UTF-8 encoded, the question about forcing the encoding on the property name is moot. Regarding the property values, it seems that the simplest solution is, for dynamic languages, to have the developer explicitly encode the string. -- Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/
pgpXBDYV_zCrX.pgp
Description: PGP signature
