On 2011-12-05 15:02, Thomas Mueller wrote:
Hi,
Unless I'm missing something, a today's JSOP parsers will be unable to
parse future messages that contain an extension defined like the above,
as they won't know how to skip over it.
What we currently don't have, and probably should add, is a way to
negotiate the format / protocol version (for example in the first message,
similar to the "HTTP/1.1" in "GET / HTTP/1.1").
But generally, parsers shouldn't silently skip over things they don't
understand, except if it's explicitly defined to be implementation
specific / optional (#pragma and such). Could you provide examples of
languages that do support such extension points?
Most XML-based formats do; the same applies to JSON -- it's the "must
ignore" pattern.
The "must understand" pattern makes it very hard to deploy new things,
as you can't use it until each recipient understands it (this is why,
for instance, the HTTP Expect header field is a big failure).
Best regards, Julian
