[OASIS Issue Tracker] (OSLCCCM-30) Specify persistence of Activity resources

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

Nick Crossley created OSLCCCM-30:
------------------------------------

             Summary: Specify persistence of Activity resources
                 Key: OSLCCCM-30
                 URL: https://issues.oasis-open.org/browse/OSLCCCM-30
             Project: OASIS OSLC Lifecycle Integration for Change and Configuration Management (OSLC CCM) TC
          Issue Type: Improvement
          Components: Configuration Management
            Reporter: Nick Crossley
            Assignee: Nick Crossley


What are the requirements for persistence of oslc_config:Activity resources in section 16 of https://tools.oasis-open.org/version-control/browse/wsvn/oslc-ccm/trunk/specs/config-mgt/config-resources.html#longoperations?

If a server is restarted, should a client be able to GET the activity resource for an operation that was accepted before the restart?
Are servers required to persist activity resources indefinitely?
If not, what is the minimum length of time after completion that they should be persisted?




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