Hi,
> -----Original Message-----
> From: Jirka Kosek [mailto:]
> > XML had a chance with an open-minded crowd of people eager
> to embrace
> > it. By and large, we utterly failed to convince them. Once other
> > options emerged, they ran there.
>
> I think that story is different. Javascript in browser
> doesn't have usable XML API (DOM is simply ... DOM), but
> evaluating JSON with eval() at that time was very easy (do
> you still remember E4X?). Also given the browser security
> model you are unable to fetch cross-site XML resources, but
> you can do the same with JSON-P. So with JSON it was possible
> to walk around limitations in browser, nothing more.
If XML had a script tag that a browser could rely on (not to say good
support for hypermedia a.k.a. the Web), or perhaps just
a <?xml-script href="..."?> processing instruction, perhaps XML
could be available to javascript programs with no CORS restriction?
That would not change the API problem...
> With
> better XML API in browser and more reasonable security model
> situation between JSON/XML in Web front-end development could
> be very different.
Regards,
Peter
