W3C home > Mailing lists > Public > public-webapi@w3.org > June 2007

Re: Recent spec change to XMLHttpRequest default Content-Type

From: Carsten Orthbandt <carsten@pixeltamer.net>
Date: Fri, 15 Jun 2007 10:56:19 +0200
Message-ID: <46725433.8010705@pixeltamer.net>
To: "Web API WG (public)" <public-webapi@w3.org>

I don't want to let loose a big discussion about best practices
here. The issue at hand is certainly solvable on our side.
But I do see a problem here with changing the spec in a way that
obviously breaks old apps that were fully standards compliant.
Sending a content type header was NOT required, now it is. But
the protocol (HTTP) didn't change at all.
I'd just like to see the XMLHttpRequest spec be changed in a
way that doesn't break existing applications. Not just because
of this content type problem but because I see a problem in the
general process here.
The change isn't needed at all. If it ain't broke, don't fix it.
Clarifying unclear sections of the spec is very good. But inverting
specced behaviour in doing so is not.
The problem with GranParadiso is certainly fixable there, but the
reason for the bug report is a deliberate spec change (or at least
I'm told so).

So to sum up:
My app was fully compliant with HTTP and XMLHttpRequest specs before
the change.
After the change it is not.
Ergo: The spec change breaks app compatibility. Which is bad.
And IMHO completely unnecessary.

If this is just the way the process is meant to work, ok. We can
certainly adapt to it. But I doubt that breaking appcompat is really
intended.


Carsten Orthbandt


pixeltamer.net
c/o Carsten Orthbandt
Baumschulenstrasse 102
12437 Berlin
+49 (0) 30 34347690
Received on Friday, 15 June 2007 08:56:34 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:57 GMT