[
Lists Home |
Date Index |
Thread Index
]
On Wednesday 19 December 2001 01:14 pm, Michael Rys wrote:
> Sorry but my use case is not serializing arbitrary binary data, but
> arbitrary TEXT data according to the originating type system (such as a
> database or a C#, C++, Java etc based webservice). Unfortunately, such
> TEXT properties may contain control characters, since the originating
> type system does not preclude them. Requiring people to base 64 encode
> TEXT just to deal with the 0.1% of cases where control characters may
> appear seems to be problematic.
In what situations do naked control characters appear in text? Control
characters are by definition control sequences.... I would generally consider
it a BUG if my character sequences contained control characters.
> And pointing out ASN.1, JNI, TDS and other binary formats is missing the
> point that the world is currently moving towards using XML for
> serialization in many contexts. And purists may scream about this, but
> SOAP/XML Protocol, WebDAV etc are not going away because of that and
> they will continue to use XML...
For the moment anyway. In the long run, all this debate will be irrelevant.
Why don't you simply make something called "BML" (Binary Markup Language) and
use that?
> PS: Gavin, please call me Michael (or spell my last name correctly, it
> is short enough after all).
Apologies.
|
