Uploaded image for project: 'OASIS Content Management Interoperability Services (CMIS) TC'
  1. OASIS Content Management Interoperability Services (CMIS) TC
  2. CMIS-172

Additional interface to query service via HTTP Get

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: REST/AtomPub Binding
    • Labels:
      None
    • Proposal:
      Hide

      To add an additional GET for query that would behave exactly as the POST for query. However, the arguments that would be added to the CMIS Query document would be added as URL arguments with the query added as a URL encoded argument for correct URL handling. The same arguments of maxItem, skipCount, searchAllVersions and statement (as q) would be added as URL arguments.

      use an uri template in the service document
      this will be required

      the output document (atom feed) of the GET vs POST to Query Collection will be equivalent (e.g., paging link relations, etc).

      Show
      To add an additional GET for query that would behave exactly as the POST for query. However, the arguments that would be added to the CMIS Query document would be added as URL arguments with the query added as a URL encoded argument for correct URL handling. The same arguments of maxItem, skipCount, searchAllVersions and statement (as q) would be added as URL arguments. use an uri template in the service document this will be required the output document (atom feed) of the GET vs POST to Query Collection will be equivalent (e.g., paging link relations, etc).

      Description

      The current interface for Query to AtomPub Protocol uses a POST to define the query. This is to allow primarily for longer queries and to simplify expressing complex queries without encoding. This is probably the edge case rather than the most frequent use case. In addition, a POST does not necessarily take advantage of standard web caching techniques and may require more complex set up by the client application to set up the query.

      If a GET call were available for expressing queries, this would be able to be constructed easily by client interfaces and results for frequently used queries could be cached. Given the choice between GET queries and POST queries, most applications would probably use the GET interface. A POST would still be needed to handle the edge case of very long queries.

        Attachments

          Activity

            People

            • Assignee:
              albertcbrown Al Brown (Inactive)
              Reporter:
              john.newton John Newton (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: