[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: New possibilites with client XSLT transformation

From: Paul Querna <chip_at_force-elite.com>
Date: 2005-03-29 21:41:48 CEST

Michael Sinz wrote:
> On Tue, 29 Mar 2005 11:16:59 -0800, Paul Querna <chip@force-elite.com> wrote:
>>Alexander Shopov wrote:
>>>Hi everybody,
>>>I have been hacking a bit on the xslt transformations of Subversion and
>>>I would like to share some results. The work is not finished yet but I
>>>hope that someone finds something useful in them. Bits to reuse,
>>>templates, whatever.
>>Hmm. It would be sweet if you had the *option* to use Server-Side
>>Then you could use mod_transform:
> Actually, with a bit of hacking, you can do this with mod_rewrite to fix
> up the behaviors. However, I really like client side transforms as the
> amount of data that needs to be sent to the client is so much less. The
> XSLT can even be cached client side but even without that, the
> HTML markup that looks nice and provides all of the links, etc, will
> be significantly larger than the XML that is sent in the XSLT case.
> Once I get to the point in the Insurrection tools where I want to
> expand the browser support I can then add mod_rewrite rules to
> detect browsers that do not support XSLT and do the work server
> side. (But I really do want client-side XSLT as it really scales
> so much better)

It is also much harder to write XSLT that runs on every browser, with
every version. Its much easier to write XSLT that runs on a known engine
(libxslt in my case). YMMV.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 29 21:42:56 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.