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


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-core message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [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=61268#comment-61268 ] 

Martin Pain commented on OSLCCORE-46:

If LDPCs' Prefer header is too coarse-grained, I'd suggest that the tool that wants this capability publicly defines a "profile" or "extension" of OSLC that requires query capabilities on ServiceProviderCatalogs, and that the tool states that servers ought to implement that profile/extension in order to allow it to scale well.
That way it re-uses what OSLC already defines, without adding extra burden on implementations that don't care. There's a downside that many implementations won't be aware of that profile/extension, but we can't put everything in the spec. Perhaps we could keep a catalog of such profiles/extensions on open-services.net, and link to there from the specs.

> 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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]