[OASIS Issue Tracker] (CMIS-793) Allow near-time discovery of changes in a repository

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Florian Mueller created CMIS-793:
------------------------------------

             Summary: Allow near-time discovery of changes in a repository
                 Key: CMIS-793
                 URL: https://issues.oasis-open.org/browse/CMIS-793
             Project: OASIS Content Management Interoperability Services (CMIS) TC
          Issue Type: New Feature
          Components: Domain Model
    Affects Versions: Proposals for 2.0
            Reporter: Florian Mueller


The getContentChanges operation allows external systems to find out what has changed in repository. That works well if the external system asks for the changes once in a while, for example in an interval of a few hours. It's not suitable for near-time discovery of changes.
Ideally, CMIS would provide some sort of subscription to repository changes, but I don't believe that would be supported by many repositories.
Instead, getContentChanges could be extended by a "timeout" parameter. With that the parameter the client can ask the server not return an empty list if no changes are present. Instead, the server waits and holds the connection until either a change can be reported or the timeout expires.  That allows a client to get near-time updates without polling the server every few minutes or seconds.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)