Eric Stockbridge wrote:
and as long as I am asking, what are the pro's con's of choosing
Apache::AxKit::StyleChooser::PathInfo
or
Apache::AxKit::StyleChooser::QueryString
AFAIK many search engines don't index pages that have a query string (with the notable exception of Google). As well, though I've never done this myself, it should be possible to use PathInfo in your stylesheets to create links to alternate styles by using relative links. For example:
<a href="printable">printable version</a>
Printable isn't an actual file, but the browser should just tack that on the end of your URI. If you use the Apache::AxKit::Plugin::AddXSLParams::Request AxKit plugin this then becomes unnecessary, because you can then access your URI parameters through XSL parameters; I personally prefer this method.
This is pure opinion on my part, but I feel that the path to your content should not include formatting options. (e.g. /articles/networking/firewalls.xml) Any formatting changes to your URI should IMHO go in query parameters, so as to not alter the path to your content (since, really, the content hasn't changed, you're just displaying it in some different way). This is why I use the QueryString StyleChooser.
--
-man
Michael A Nachbaur
The best way to predict the Future is to invent it.
PGP Public Key at http://www.nachbaur.com/pgpkey.asc
PGP Key fingerprint = 83DC 7C3A 3084 6A21 9A3F 801E D974 AFB4 BFD7 2B6F
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
