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

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

     [ https://issues.oasis-open.org/browse/OSLCCCM-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Crossley updated OSLCCCM-30:
---------------------------------

    Proposal: 
Each Activity resource MUST be persisted by a server (including over a restart) for a minimum of 24 hours after completion, or until explicitly deleted by a client
 
Clients SHOULD delete each Activity created by a long-running operation soon after the client has seen the completion of the activity, or when the client is no longer interested in the result. Servers MAY deny clients access to delete Activity resources including but not limited to activities still in progress, or activities not created by that client, or MAY require clients to have a specific role or permission to delete activities.


  was:
Each Activity resource MUST be persisted by a server (including over a restart) for a minimum of 24 hours after completion, or until explicitly deleted by a client
 
Clients SHOULD delete each Activity created by a long-running operation soon after the client has seen the completion of the activity, or when the client is no longer interested in the result. Servers MAY deny clients access to delete Activity resources not created by that client, or MAY require clients to have a specific role or permission to delete other Activities.



> 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
>              Labels: ready-for-vote
>
> 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)