Stefan,
Stefan Burkard wrote on 07/12/04 11:00 AM:
---> ok, thanks for the advice. additionally i saw that the double-version only occurs when i first put in the document. when i put in a new version of an existing doc, it just creates ONE new version.
Hmm, maybe this wasn't what I thought it was, but I guess that might depend on which client you used to create the document. I think I'd only ever seen 1 version created myself, but I honestly wasn't paying that much attention.
just two other questions:
- what are the consequences for dumb-client-documents that are checked out (automatically), but not checked in (manually) again?
The consequence would be that a dumb client would never be able to actually create a new version of your document. You would have to perform the checking from a "smart client". This is normally not a problem if you have some sort of CMS/workflow interface to control the checkin features. You could leverage the "ease of use" of web folders or the KDE webdav:// protocol for day-to-day updates rather than a clunky web interface.
I have had locking issues with dumb clients though, so if something gets locked by a smart client after an auto-checkout it will automatically get checked-in when the lock is removed again from the smart client. This is per the spec, but not always desired program behaviour.
Long and the short of it, use a smart client for all checkout/checkin/uncheckout/locking.
- what is the versioncontrol-method for? to activate and disactivate version-controlling on a document?
If you don't use the "auto-version-control" parameter, yes, this is the method that would be called to place a resource under version control. We had an earlier discussion about how to take a resource out of version control and I think the consensus was you "couldn't". I think you would have to create a new resource that was specifically not under version and fill the contents/metadata from the last version.
I have spent quite a bit of time investigating how all of these properties work with or against each other. The gist of everything is that dumb clients just mess everything up or make things more complicated. The only upside is easier use by the end user because you can have drag-drop, remote editing, remote saving, etc.
I think you are wading your way through :)
Tim
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
