Comments on: jQuery API draft http://bassistance.de/2006/11/10/jquery-api-draft/ Jörn Zaefferer on Bass, Geeks and Rock'n'Roll Tue, 31 Jan 2012 11:18:41 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Jörn http://bassistance.de/2006/11/10/jquery-api-draft/comment-page-1/#comment-899 Jörn Sat, 11 Nov 2006 18:44:01 +0000 http://bassistance.de/2006/11/10/jquery-api-draft/#comment-899 XSLT is quite powerful, too. With the current setup, only the raw XML file and the XSL file is transfered to the client, the rendering happens on the client side. We could still pre-render it on the serverside and only send the rendered XHTML to the client. Developing is definitely easier when the rendering is happening on the client side, because there is no serverside scripting involved. XSLT is quite powerful, too. With the current setup, only the raw XML file and the XSL file is transfered to the client, the rendering happens on the client side. We could still pre-render it on the serverside and only send the rendered XHTML to the client.

Developing is definitely easier when the rendering is happening on the client side, because there is no serverside scripting involved.

]]> By: Anders http://bassistance.de/2006/11/10/jquery-api-draft/comment-page-1/#comment-898 Anders Sat, 11 Nov 2006 18:30:21 +0000 http://bassistance.de/2006/11/10/jquery-api-draft/#comment-898 I'm curious what the advantages are of using XSLT over rendering a (X)HTML page from the XML file. I've actually done that with some simple PHP, and to me it's seems like you have much more power that way. I’m curious what the advantages are of using XSLT over rendering a (X)HTML page from the XML file. I’ve actually done that with some simple PHP, and to me it’s seems like you have much more power that way.

]]>