The files you talk about are only one half of the resource information. While they contain the actual content, there is another tree containing meta information. Now, your tree contains all versions of content and as each file needs a different name the version number is appended to the original resource name. This results in names ending in _1.0 etc. If you switch if off, all versions would be saved to the same file overriding each other. Although, when versioning is turned off, it might be save to omit the version number. I could add a switch for this...
Note that the 'versioning' Oliver talks about here is slide-internal versioning. Most users do not use that - if they use versioning, they use WebDAV/DeltaV versioning, which does NOT use the slide-internal versioning to work.
So you can continue to safely use DeltaV if you want with this stuff turned off.
To see if this helps disable it manually in org.apache.slide.store.txfile.TxFileContentStore by changing every line that looks like
String revisionUri = uri.toString() + "_" + revisionDescriptor.getRevisionNumber();
to
String revisionUri = uri.toString();
Talking about ACLs. There currently is no store that uses access control of the file system.
I'm not really sure how one would do this... Is there any way with the Java APIs to get FS ACL information? I'd expect not, since it's very platform specific (and needs to remain so - the semantics differ too much across various platforms for a unified API to be really useful - note all the complexity in the webdav ACL specification, and even then that leaves a LOT up to implementation choice).
So (if I'm right that Java doesn't directly give us access to this info) you'd need to use JNI (or a seperate native helper process?) to do it. That bit doesn't sound like too much fun...
You'd also need to run it as a superuser of some form (depending on the platform), to actually access the files on behalf of the appropriate (authenticated) user, which is not a very attractive proposition to most sysadmins, for good reasons. Another native helper process?
To make this useful, I think we'd need some fairly major surgery to slide's webdav-acl implementation, too, so that the semantics it uses (and advertises) are store-dependent (this would require pluggable security implementations as well, but we've already got that).
It'd be an interesting project, however.
Mike
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
