[OASIS Issue Tracker] (OSLCCCM-22) Provide a way for a client to discover the configuration used to resolve a request

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

Nick Crossley updated OSLCCCM-22:
---------------------------------

        Summary: Provide a way for a client to discover the configuration used to resolve a request  (was: CLONE - Provide a way for a client to discover the default configuration for a given configuration provider)
       Assignee: Nick Crossley
    Description: The spec allows a client to provide a configuration context using either a header or a query string, but there is no way for the client to discover if this configuration was actually used, or which contribution to a global configuration was used, to satisfy the request.  (was: The spec allows a server to provide a default configuration context, but no way for the client to discover what this default is. It would be useful for the client to be able to do so.)
       Proposal: Servers SHOULD use the Configuration-Context header in any response to a request for a single versioned resource, indicating which local configuration was used to satisfy that request.  (was: Provide a link in the service document that references a ConfigurationSettings resource, which has a property identifying the default configuration. A GET on this resource would return this property (amongst any others). A PUT on this resource MAY be supported.)

> Provide a way for a client to discover the configuration used to resolve a request
> ----------------------------------------------------------------------------------
>
>                 Key: OSLCCCM-22
>                 URL: https://issues.oasis-open.org/browse/OSLCCCM-22
>             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
>            Priority: Minor
>
> The spec allows a client to provide a configuration context using either a header or a query string, but there is no way for the client to discover if this configuration was actually used, or which contribution to a global configuration was used, to satisfy the request.



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