(!) Rather than use interceptors, every method in the adapter that modifies the underlying RDBMS also reindexes the file. Principally because my client is mostly interested in the "meta-meta"
property of
whether anything (acl, lock, properties) have changed, so
as
to cache successfully. Change propogation to children I
simply ignored
(because for a relational system, which is what I was
after, there's no
such thing as a definitive parent/child relationship).
I'm not sure I understand what you mean here, can you elaborate more?
OK. By "relational filesystem" I meant a hierarchical view of a
filesystem where the "model" structure , folders & children, is
dynamically constructed from an underlying traditional filesystem, e.g.
a standard Slide store.
So you can show a view - say /users/john/recent/projects/myProject
of the total file system which is filtered to show only files for which john is the editor and have been modified in the last 10 days. Sort of like workspaces, but completely property-defined.
And that "view" (from the data point of view) is just a normal folder
(to the client).
I've just got it working, and I'm already finding it useful.
Sounds interesting. So this is like a view in a releational database? Something like a "froozen" query?
Oliver
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
