Uploaded image for project: 'OASIS OSLC Lifecycle Integration Core (OSLC Core) TC'
  1. OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
  2. OSLCCORE-46

Discovery of services through query rather than LDPC traversal

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Component/s: None
    • Labels:
      None
    • Proposal:
      Hide

      One way of making it easier for an OSLC client to discover services of interest would be to have a query capability for services. That way the LDPC traveral happens on the server.

      Show
      One way of making it easier for an OSLC client to discover services of interest would be to have a query capability for services. That way the LDPC traveral happens on the server.
    • Resolution:
      Hide

      I added the following paragraph at the end of section "5. Discovery Capabilities":

      <p>This specification specifies how servers respond to discovery requests through LDPC Link headers or ServiceProviderCatalog and/or ServiceProvider resources. It does not specify how servers organize their LDPCs, how they make distinguished LDPCs known to end users to start the discovery process, or how servers provide efficient access to discovery information that may be distributed over many LDPCs managed by the server. Servers may choose to support the OSLC Query capability on OSLC LDPCs and discovery resources in order to facilitate access to discovery information.</p>

      Is this sufficient to close this issue?

      Show
      I added the following paragraph at the end of section "5. Discovery Capabilities": <p>This specification specifies how servers respond to discovery requests through LDPC Link headers or ServiceProviderCatalog and/or ServiceProvider resources. It does not specify how servers organize their LDPCs, how they make distinguished LDPCs known to end users to start the discovery process, or how servers provide efficient access to discovery information that may be distributed over many LDPCs managed by the server. Servers may choose to support the OSLC Query capability on OSLC LDPCs and discovery resources in order to facilitate access to discovery information.</p> Is this sufficient to close this issue?

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              jamsden James Amsden
              Reporter:
              DavidHoney David Honey
            • Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: