--- Remy wrote:
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 ?
---
I'm not certain I know enough about the Slide internal architecture to give
meaningful advice there. How would you be splitting up the functionality? An
pre- and a post-storage filter?
---
Yes, but it wouldn't hurt to be able to do it. The point of the filtering is
to make things more flexible.
---
True. I'm just not sure what the "WebDAV-ish" way to accomplish that sort of
access to dynamic content is. I seems to recall from my last breeze through the
spec that they expected links to be one way to "discover" the source from the
dynamic page -- but, then, that assumes that the software serving the dynamic
page knows enough about WebDAV to inlcude the link...
---
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.
---
Not that I'm an expert, but I'd say that unless you have definite cases in mind
where these sorts of filters would be useful, you might want to hold off. Sure,
this sort of composition makes things more flexible, but it also makes them more
complicated and hard to understand. If you aren't sure of the benefits, is it
worth the complexity and additional implementation effort?
Sixten
