OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-ccm message

[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:comment-tabpanel&focusedCommentId=62585#comment-62585 ] 

Nick Crossley commented on OSLCCCM-22:
--------------------------------------

The contribution is a configuration of a component. There is an immutable association between a configuration and its component, so identifying the configuration identifies the component.
The proposal is to return a header identifying the local configuration used to resolve the reference to the artifact. The value to the client is that the response identifies that local configuration, and hence its component, without the client having to replicate the algorithm used by the GC provider to determine the correct local configuration from the global configuration, and without the client having to obtain all the data (the GC structure) used by the GC provider when applying that algorithm.

> 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: work_required
>
> 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]