> >
> > - Add new interfaces by cascading XSLT and/or XPathScript and/or XSP
> > stylesheets
>
> One thing to remember is that XSP isn't a stylesheet - it's more like
> code. I guess think of it as a better ASP or JSP or PHP.
ok.. this how it works right?
a request for document.html arrives
document.html is an xml file that uses the taglibs that i defined
using xpathscript or xslt.
the taglib creates an xml file that i can transform using one of
many stylesheets choosen using AxKit's media type and associated
logic.
if i want to change the appearance of my site, i pay a fancy pants
designer gobs of money to write xsl stylesheets based on a dtd of the
xml that my xsp/taglib generates.
kewl.
> > Can I write a Provider subclass that only handles XML document requests?
>
> requests go through the same provider, which is only dependant on the
> apache config mappings for a particular request. I.e it won't make any
wouldn't it be possible to subclass one of the Providers and simply
pass along requests for things that I don't want to handle?
> The aim is to clean this up a bit by allowing scheme oriented providers,
> so you'll be able to map the request to xdc://some/path and have your XDC
> provider pick it up, but it's still just an idea and hasn't been specced
> out fully yet.
that would work, but i would prefer to see a design that is more
standards based.
what i want is a way to dynamically provide the xml that will be used
for a given request. now that i understand more clearly, i think that
a taglib is the right tool, but being able to easily define and extend
providers seems like a really nice feature.
Thanks for your thoughts, Aaron
--
aaron ross . alias i, inc
email . [EMAIL PROTECTED]
phone . 215 545 6428
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
