Uploaded image for project: 'OASIS Content Management Interoperability Services (CMIS) TC'
  1. OASIS Content Management Interoperability Services (CMIS) TC
  2. CMIS-196

Pessimistic Locking

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Deferred
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Proposals for 2.0
    • Component/s: Domain Model
    • Labels:
      None
    • Proposal:
      Hide

      A very simple first approach would be to have additonal methods in the object service: LockObject(), UnlockObject(), IsLocked(), GetLockOwner(), GetLockedObjects(). Questions are: on documents only? on folders? recursive? expiration of locks? Optional?

      Show
      A very simple first approach would be to have additonal methods in the object service: LockObject(), UnlockObject(), IsLocked(), GetLockOwner(), GetLockedObjects(). Questions are: on documents only? on folders? recursive? expiration of locks? Optional?

      Description

      After some workshops around CMIS integration scenarios it appears that the lack of pessimistic locking might be an issue in some situations. There are some use cases (for example in SAP) that require a hard lock on an object and there are related standards like WebDAV that have support for locks which can not be mapped to CMIS today. The current spec proposal was designed intentionally this way and that there are a couple of issues with this introducing this. However I would like to get a better picture how much demand there is in the TC for having such a feature in the CMIS domain model.

        Attachments

          Activity

            People

            • Assignee:
              ethang Ethan Gur-esh
              Reporter:
              jhuebel Jens Hübel (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated: