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?
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)?
thanks, arne
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]