[
Lists Home |
Date Index |
Thread Index
]
- From: Didier PH Martin <martind@netfolder.com>
- To: Xml-Dev <xml-dev@xml.org>,Aleksi Niemelä <aleksi.niemela@cinnober.com>
- Date: Wed, 22 Nov 2000 08:55:30 -0500
Hi Aleksi
Aleksi said:
I'm sorry to ask if this is too trivial, but what do you mean by "able to
respond to an XML document request"?
Didier replies:
Sorry this wasn't clear. What I mean is: a server able to process an HTTP
GET for an XML document
(Ex: GET /myfolder/mydoc.xml).
Because most of the browsers do not support XSLT local processing, the
server recognizes the client capacities and adapt to it by sending the
proper format instead of the original XML document. For instance, in the
case of an HTML browser, the server sends an HTML document, in the case of a
WML browser the server sends a WML document and in the case of a VoiceXML
browser the server sends a VoiceXML document. Hence, the XML document is
firstly transformed from its original XML vocabulary and structure to a
rendering format that the requesting browser understands.
If, for instance, you access the following site with an HTTP GET for an XML
document (like below)
http://axkit.com/news/2000/10/02/01.xml
The server does not send to the requester an XML document but more an HTML
document. Thus, a transformation has occurred on the server side to
transform the document form its original XML format to a rendering format
(in the case you access the document with an HTML browser, it is transformed
into HTML).
So, any other real stuff in addition to:
http://www.infoworld.com
http://www.axkit.com
http://www.pdamd.com/
and the XML sites listed by cocoon?
Hummm, the list is increasing. Sounds like these people know how to master
the transformation process.
cheers
Didier PH Martin
|