The central idea with the JSONRequest is that it is exempted from the Same
Origin Policy. It allows for exchanging data with a server in any domain that
specifically accepts JSONRequests.
In order to be exempted from the Same Origin Policy, there are several
restrictions on JSONRequest in
Quoting Douglas Crockford [EMAIL PROTECTED]:
The central idea with the JSONRequest is that it is exempted from the
Same Origin Policy. It allows for exchanging data with a server in
any domain that specifically accepts JSONRequests.
In order to be exempted from the Same Origin Policy, there
Henri Sivonen wrote:
Single select:
Is it conforming for an option to be both selected and disabled? (I
think it shouldn't be conforming.)
I agree with that.
And analogously: Is is conforming for a radio button to be both checked
and disabled if the whole set is not disabled? (This one is
Gervase Markham wrote:
Douglas Crockford wrote:
I have modified the JSONRequest proposal so that the Content-Type in
both directions must be application/json/request.
Er, why? Having two slashes in a content type is either extremely weird
or completely illegal (glancing at the RFC, I'm not
