Google AJAXSLT
Those hackers over at Google are at it again. Seems that they’ve created both an XPath parser and XSLT engine written completely in JavaScript. The project is called Google AJAXSLT, which is sort of a weird name, but lends itself to the belief that it will be useful (and necessary) for Ajax applications.
Apparently, this Google AJAXSLT is used to make Google Maps work on browsers that don’t support client-side XSLT such as Opera. Now, they’ve released it to open source for all the world to play with.
Disclaimer: Any viewpoints and opinions expressed in this article are those of Nicholas C. Zakas and do not, in any way, reflect those of my employer, my colleagues, Wrox Publishing, O'Reilly Publishing, or anyone else. I speak only for myself, not for them.
Both comments and pings are currently closed.
2 Comments
Is it realy a good idea to stream xml to your own aplication and then transform it again? I can understand offering a xml feed for others but is it not easier to send the data for your own application in the correct format in the first place?
Glyn on July 8th, 2005 at 10:23 am
Well, I assume they're doing it because it takes load off of the server. I'd imagine that Google's servers are field tons of requests every second and the call to transform an XML document can take longer than a normal request because it has to parse the XML, parse the XSLT, then run the transformation.
Nicholas C. Zakas on July 8th, 2005 at 1:57 pm
Comments are automatically closed after 14 days.