Re: XSLT version of TAL, pushing caching to the client

Tino Wildenhain <[email protected]> Sun, 24 Jul 2005 12:02:41 +0200
Newsgroups gmane.comp.web.zope.page-templates
Message-ID <[email protected]>
Am Freitag, den 22.07.2005, 18:58 -0400 schrieb Brad Clements:
> On 22 Jul 2005 at 23:34, Tino Wildenhain wrote:
> 
> > 
> > I wonder what this buys you other then the well recognized XSLT-label.
> > XHTML+CSS where the XHTML is produced by simple and understandable TAL
> > can do all you would need. But thats just me...
> > 
> 
> But server-rendered html cannot do anything except have the client 
> cache the entire page. If you don't resort to xmlhttp request, then the 
> client only gets what you sent as fully rendered html.
> 
> therefore, only entire pages are cached, not parts, nor the backing data 
> that makes the page (like the blogroll or nav tab from my previous 
> example).

Is there an online visible example where this works like that?
Which clients support xslt like this (e.g. with subrequests)

How is this different from loading and caching CSS files?