On Jan 7, 5:26 pm, John Resig wrote:
> Since we're going to be using JSON.parse, which throws an exception
> (and triggers the Ajax error handler) it should probably be consistent
> across platforms.
well it might not be consistent across platforms, since in CHROME
window.JSON.parse will happil
@John, I did not say it clearly, so I will do it now: I agree 100%
with no-compromise approach to "non-standard" (aka illegal) JSON
strings. It is only that in reality, there are well known and
(commercial) paid for RESTfull services, which return this wrong kind
of JSON. Especially this kind :
@Juilan, believe me I was on the JSON secuirty issue more than once
with Mr Crockford.
The issue I have pointed out is that one can have whole functions as
symbol names in JSON.
And then execute them with an inoccently looking "sleeper"
On Jan 7, 2:49 pm, Julian Aubourg wrote:
> What I'm worried
