On Thu, Aug 22, 2013 at 8:41 AM, Gordon Sim <g...@redhat.com> wrote: > On 08/21/2013 10:43 PM, Justin Ross wrote: >> "If I put a binary value in a map and encoded it some of the time it >> might be valid utf8, other times not." This shouldn't be allowed to >> happen, IMO. You meant it to be a binary value--we have to find a way >> to capture and preserve that information. > > I believe the point was that for an application sending binary data via the > ambiguous string type (between two processes in languages that have such a > type), if that was encoded on the wire as str16 (i.e. utf8) it could lead to > subtle bugs. > > Testing could work until the actual binary payload was changed in some way > such that it was not valid utf8.
Right. I'm saying that sucks, so don't do that. For instance, we could ask our users to use a 'Data' class to input arbitrary bytes, and otherwise treat ambiguous strings as textual. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
