[OASIS Issue Tracker] (OSLCCORE-46) Discovery of services through query rather than LDPC traversal

[ https://issues.oasis-open.org/browse/OSLCCORE-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61560#comment-61560 ] 

Martin Pain commented on OSLCCORE-46:
-------------------------------------

Re: text in "resolution" field.

I think that section (section 5, before section 5.1) is getting a bit long, but I think that text adequately addresses the issue.

> Discovery of services through query rather than LDPC traversal
> --------------------------------------------------------------
>
>                 Key: OSLCCORE-46
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-46
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: New Feature
>            Reporter: David Honey
>            Assignee: James Amsden
>
> The proposed 3.0 discovery requires that clients traverse a hierarchy of LPDCs to find service(s) of interest. Some OSLC 2.0 clients may [erroneously] assume they can discover such services through a single GET of the service provider catalog. When the OSLC client has significant network latency with the OSLC provider, having to iteratively GET LDPCs might lead to slow discovery performance. 



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