> No, that's not accurate -- there was a misunderstanding in some blogs,
> but I think it's been cleared up now.
Ah, thanks for the clarification.
> Note also that like XML, JSON is purely declarative and (thus) not
> Turing-complete -- to make JSON executable, you have to wrap it with
> JavaScript, just as you would have to wrap XML to make it executable.
> It just happens that the wrapping is more convenient with JSON.
The point is that JSON *is* JavaScript, and that clients are implementing
JSON by calling eval. Are there are any browser clients that have an
"evalJSON" method? Since XML is its own syntax :) this carelessness can't
happen.
/r$
--
STSM
Senior Security Architect
DataPower SOA Appliances
