> Remy said:
>
> > Conditional processing is an important feature, but to be really
flexible it
> > has to use the same kind of semantics that approvals and notifications
will
> > use (read : be a user defined process).
> >
> > In the meantime, it would probably be a good idea to define a simple
> > specialized filter API for the WebDAV servlet (probably a set of
interfaces
> > would do). What do you think ?
>
> Remy, could you please explain in general terms what the filter API
> might be able to do? thanks .. Jason
I would put in methods like :
void filterContent(SlideToken token, Namespace namespace,
NamespaceConfig namespaceConfig,
NodeRevisionDescriptors revisionDescriptors,
NodeRevisionDescriptor revisionDescriptor,
NodeRevisionContent revisionContent);
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.
I'm waiting for feedback on this, and in particular what kind of additional
methods would be needed.
Remy
Note : Since the filter would get the namespace as a parameter, it has to be
trusted code. The namespace is given as a parameter so that the filter can
access other objects as needed. I don't know if that functionality is really
needed.
