I've been doing my dynamic stylesheet choosing using
AxAddDynamicProcessor. This has some drawbacks since you have to muck
around with axkit_cache_extra in an earlier apache phase, otherwise your
stylesheet processor might never get hit.
So i rewrote some as AxPlugin's. This works great for anything that has a single stylesheet. But can an AxPlugin also affect a pipeline of stylehsheets like the @styles returned by a Dynamic Processor?
For that matter is ther an API of what you can do with an AxPlugin?
Pretty much everything you can do with an AxPlugin is by modification of notes/pnotes (or other parts of the Apache requestrec). I don't think you can modify the styles that way, unless you do it and pick it up later in some further custom code.
Finally, the description in the docs are "This allows you to setup things like sessions, do authentication, or other actions that require no XML output, before the actual XML processing stage of AxKit." Are there any benefits of doing this as an AxKit plug-in rather than some other Perl*Handler, aside from being able to stack them (although some of the non-content Perl*Handler's are stackable as well)?
No, it's just designed for people who don't know about mod_perl (and thus don't need to know about mod_perl).
Matt.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
