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

Nick Crossley commented on OSLCCORE-119:
----------------------------------------

Nick Crossley added a comment - 02/Jun/16 10:56 AM

Client apps could use this information in diagnostic screens, or logs, to help diagnose problems. Given the number and frequency of requests issued by a client, it is unlikely that it would be useful to try to display a location response continuously. 

Remember that GCs form a hierarchy - a user would not always assemble a GC with the local configs as direct contributions - they may assemble a GC from other GCs, which might be managed by other config leads. So a GC might have its contribution tree changed by a third party at any time.


> 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)