[Home] [By Thread] [By Date] [Recent Entries]

  • From: Bjoern Hoehrmann <derhoermi@g...>
  • To: Didier PH Martin <martind@n...>
  • Date: Sun, 09 Sep 2001 02:02:35 +0200

* Didier PH Martin wrote:
>Here is what a modern server can do:
>
>a) recognize the user agent.
>
>b) For most of the browsers, the server performs XSLT transformations on the
>server side. In the case of IE 6 or Mozilla (still work in progress) it
>performs the transformation on the client side.

And this is better because...?

>The bottom line is: the server can determine is the user agent support XSLT
>or not.

Yes? Sounds cool. How is this supposed to work? Is there some new web
service XSLT transfer protocol that provides this information? I thought
all information the server has are those in the HTTP request and they
certainly don't carry these information.

>If yes, the process can occur at the edge or at the client site.
>Otherwise at the server side. As more client support XSLT transformation,
>less server load you'll have. Is using a 1 ghz client to perform dummy
>rendering a best way to use resources?

Maybe, maybe not. Why does this matter?
-- 
Björn Höhrmann { mailto:bjoern@h... } http://www.bjoernsworld.de
am Badedeich 7 } Telefon: +49(0)4667/981028 { http://bjoern.hoehrmann.de
25899 Dagebüll { PGP Pub. KeyID: 0xA4357E78 } http://www.learn.to/quote/

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member