Specifies if a revised document is visible to the author and users with Read permission to the content item. The default is 12000 milliseconds (12 seconds). If a lock is falsely expired, it can cause duplicated effort (although it should not have any long term impact on the state of the Content Server instance). The larger the value, the more likely that high activity (which could keep a touch request delayed for many seconds) on the network drive will cause a Content Server instance to falsely report a lock as having expired. The smaller the value of this setting, the quicker that locks can alternate between Content Server instances. In order for the lock to persist, the timestamp on the file must change periodically otherwise any contending Content Server instance will treat the lock as an expired lock. The Content Server instance will also touch any locks it is maintaining twice during this interval.Īn archive lock is created by placing a lock file into an appropriate directory. Defines the time that a contending Content Server instance will wait before it will treat an archive lock file whose timestamp has not changed as having expired.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |