> > I'm inclined to second that, except I'm not sure whether there are > > conceivable non-ASCII non-UTF strings that include valid UTF16 > > characters. The parser could not discern between UTF and binary then, or > > could it? >
Correct. But it shouldn't need to. Practically, I don't know what PSON does, but my expectation is it would > treat > it as UTF-16 and break when that didn't actually match the correct use > pattern > for binary data The present intent for PSON is to not make assumptions about the internal format of strings; to treat them as binary data and transfer them accurately. As the transports layer doesn't interpret the payload in any way, it doesn't need to (and shouldn't) try to improve it, clean it up, "fix a few things for you", etc. on the way through. -- 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.
