Although I'm far from clear on the details at this point, my
understanding is that by changing the application that generates my web
pages to instead generate XML, I will later be able to selectively apply
XSL style sheets based on the type of device accessing my site. This
will greatly simplify the application by offloading presentation, and
will make graphic design changes much simpler (I don't even use CSS
right now). I would like to be accessible by PDAs and such now, and who
knows what the future holds.

Performance is not a big concern since everything is cached. But that's
why I was interested to know if the style sheets could be applied
locally to generate XHTML pages into the cache instead of leaving it to
an unknown, that is, whether the visitor's browser understands XML/XSL.

> -----Original Message-----
> From: Nathan M. Andelin

> Isn't XSL really a programming language with looping 
> constructs, conditional
> logic, and so forth?  Well, such is the case with object oriented
> vocabulary, which sadly tends to get more convoluted over time.
> 
...
> 
> Consider that servlets or JSPs typically transform SQL result 
> sets to XML,
> then another program (XSL) is evoked to transform the XML into HTML.
 
NOTICE: This E-mail may contain confidential information. If you are not
the addressee or the intended recipient please do not read this E-mail
and please immediately delete this e-mail message and any attachments
from your workstation or network mail system. If you are the addressee
or the intended recipient and you save or print a copy of this E-mail,
please place it in an appropriate file, depending on whether
confidential information is contained in the message.



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.