[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [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: --------------------------------- Proposal: Update: current suggestion is to undo the following change. The following text was added to the draft spec: 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. was: The following text was added to the draft spec: 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. > 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 > Labels: ready-for-vote > > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]