News for hackers. Stuff that matters.
Re:Providing APIs for content-driven websites by eCa on Sunday October 07, 2012 @06:33PM (#4624665)
I once built a very tiny web application with the structure of the GUI in an xml file that was transformed (on the server) with xslt. I probably did one or two things wrong, but it was a complete misery. It could only be worse if the transformation was done in the uncontrollable environment on the client.
Re:Providing APIs for content-driven websites by lazyjones on Sunday October 07, 2012 @08:57PM (#4625042)
On the client side, there were lots of bugs, some are discussed in this SO thread:

http://stackoverflow.com/questions/274290/any-big-sites-usin...

You'd have to do hacky browser xslt detection as detailed here: http://www.informit.com/articles/printerfriendly.aspx?p=6779...

XML in this context apparently pretty much died because of too many badly written parsers, libraries and browsers - and to some extent probably also because dominant search engines would not index XML files properly (see http://news.oreilly.com/2008/06/why-xslt-support-in-the-brow...).

But nowdays at least there are some reasonably portable solutions like http://archive.plugins.jquery.com/project/Transform (but that's unnecessarily slow).

On the server side, it should be fairly simple, unless you hit bugs/deficiencies (like wasting memory / leaks) in libraries ...