> Most content providers who use XML transform it on the server because most
> browsers in use today do not support XSLT well or at all.
They transform it on the server, because that's EXACTLY how it was
meant to be delivered.
XML is nothing more than an empty bucket, and has absolutely nothing
at all to do with HTML or the web, other than the fact that both XML and
HTML are extensions derived from SGML. Contrary to popular belief, XML is
not "the next HTML". XML doesn't do _anything_ on its own, it's simply a
container, nothing more. With the proper DTD and optionally XSLT to
transform it, the content that the XML "bucket" describes, can then be
useful to 'n' number or types of clients.
> That and the fact that by transforming it on the server means they
> maintain control over which client views what content.
Exactly, and this is how it was intended to be done. Displaying
actual XML content on port 80 is just a blatent misuse (or misunderstanding)
of the technology.
d.
_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
