D -- A JSON "message" is explicitly specified to be a UTF-8 encoded string of > characters, so anything that tries to convey data outside that encoding > should > rightly be pushed back by upstream. >
That's not the issue. We aren't talking about the message here, but the values of string fields inside the messages. They are supposed to be able to contain arbitrary binary data, and JSON even defines escapes (\x##, \U####, \###, etc.) for representing such data. > (I would probably have aimed to transform whatever 8-bit locale encoding > into > UTF-8 and decoded back on the client side, so that *only* the very edges > of > the system know anything about non-Unicode data. And in the case that the data is, say, a jpeg? Or an executable? Not everything can be represented in UTF-8; sometimes you really do want to transfer something and have it show up identically on the other end and not have the transport layer do you any Unicode Favors(tm). -- Markus ----------------------------------------------------------- The power of accurate observation is commonly called cynicism by those who have not got it. ~George Bernard Shaw ------------------------------------------------------------ -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
