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

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

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

Nick Crossley updated OSLCCORE-119:
-----------------------------------

      Proposal: 
The following approach was suggested, and briefly included in the draft, but then removed:

Where the response to a GET is a single versioned resource, the server SHOULD include a <code>Configuration-Context</code> header indicating the precise configuration in which that resource was found. 
Note this is frequently not the same as the context on the request: the context on the request is likely to be a global configuration, while the context on the response, if present, MUST be the leaf-level provider-specific configuration contributed to the requested context. 
    Resolution: Defer from consideration in 1.0

> Provide a way for a client to discover the configuration used to resolve a request
> ----------------------------------------------------------------------------------
>
>                 Key: OSLCCORE-119
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-119
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Improvement
>          Components: Configuration Management
>            Reporter: 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)