Michael Smith wrote:
Oliver Zeigermann wrote:
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.
I do not think so, even though I may be completely wrong. The WebDAV/DeltaV versioning actually *does* seem to use slide-internal versioning, even though not exactly in a way one would expect. E.g. properties are versioned in revision descriptors and content is versioned using different version numbers, although *only* in the history folder. Quite confusing, I guess... Maybe too confusing, so I might well be very wrong here...
Oliver
This is entirely possible - I know the main part of the versioning is not done using slide's versioning, but I'm not certain about all the details of how the DeltaV stuff stores data/properties in the history directory.
Mike
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
