> --- Remy wrote:
> That method will be called (for all registered filters) just before
storing
> (or creating) content in the Store. Filters will be declared in
Domain.xml.
> ---
>
> What about filtering content on the way out?
I wasn't sure that post filtering could be useful, but I guess it wouldn't
hurt.
> One of the things that I'm looking at is using Slide to allow users to
manage
> web sites that may use JSP or Resin's XTP (XML Template Pages). People
should be
> able to upload/manage their pages, but what users see should be the result
of
> the page's execution, not the source.
Ok, you have a rock solid point there.
So at least two methods then, one called just before storing, and one just
after.
Also, what would be better : one interface holding all the methods (with an
abstract implementation so that you don't have to implement all of those
which aren't useful), or multiple interfaces ?
> Though it seems like the thing to do would be to leave the JSP/XTP/etc.
engine
> as the site root servlet ('/'), and create a separate WebDAV access (like
the
> default /webdav mapping in slide.war). That way each engine only handles
what
> it's best at.
Yes, but it wouldn't hurt to be able to do it. The point of the filtering is
to make things more flexible.
I'm wondering if filters would be useful in other components (structure,
lock, security), or if just filtering on content (which is definitely the
most useful) is enough.
Remy
