For python, this is indeed the solution we used when a user wanted the Java client to recognize a python string sent in a map or an application property.
On Fri, Aug 16, 2013 at 8:55 AM, Gordon Sim <g...@redhat.com> wrote: > On 08/16/2013 01:15 PM, Darryl L. Pierce wrote: > >> On Mon, Aug 12, 2013 at 08:52:20PM +0200, Jimmy Jones wrote: >> >>> I'm a user of binary data in maps! >>> >>> I created the patch to handle UTF8 in perl. Removing the check will >>> cause non-UTF8 strings to be casted into UTF8 which is probably a bad idea >>> unless by luck they are 7 bit ASCII. >>> >> >> Hey, Jimmy. I've been in training this week so haven't been able to >> respond. >> >> I reverted my changes, and would like to collaborate with you on a >> better, more considered solution to the problem of sending properties >> from Perl and the other dynamic languages. >> > > For Perl, what was wrong with the original code (as it is now you have > reverted your changes)? It looks like that allows one to explicitly pass > utf8 strings that will then be encoded as such. Whats the problem statement? > > For python, might one solution be to encode unicode strings as utf8? Again > that at least gives you the ability to control what happens. > > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > dev-unsubscribe@qpid.apache.**org<dev-unsubscr...@qpid.apache.org> > For additional commands, e-mail: dev-h...@qpid.apache.org > >
