[OASIS Issue Tracker] Created: (CMIS-172) Additional interface toquery service via HTTP Get

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Additional interface to query service via HTTP Get
--------------------------------------------------

                 Key: CMIS-172
                 URL: http://tools.oasis-open.org/issues/browse/CMIS-172
             Project: OASIS Content Management Interoperability Services (CMIS) TC
          Issue Type: New Feature
          Components: REST/AtomPub Binding
    Affects Versions: Draft 0.61
            Reporter: John Newton
            Assignee: Al Brown


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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira