OSLC paging should support POST with an application/x-www-form-urlencoded body

XMLWordPrintable

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major
    • Component/s: Core
    • None
    • Hide

      The Core spec should describe an oslc:ResponseInfo, and for resource paging that a paged response to a POST with a application/x-www-form-urlencoded body should include a response info with both oslc:nextPage and a new property, oslc:postBody, whose plain literal value is an application/x-www-form-urlencoded string representing the query parameters. If a client performs a GET to a paged resource, then oslc:postBody SHOULD not be included. If a client gets a paged resource using POST with a application/x-www-form-urlencoded body, the response info SHOULD include a oslc:PostBody and the client SHOULD fetch that next page using POST with a www-form-urlencoded body read from the oslc:postBody.

      Show
      The Core spec should describe an oslc:ResponseInfo, and for resource paging that a paged response to a POST with a application/x-www-form-urlencoded body should include a response info with both oslc:nextPage and a new property, oslc:postBody, whose plain literal value is an application/x-www-form-urlencoded string representing the query parameters. If a client performs a GET to a paged resource, then oslc:postBody SHOULD not be included. If a client gets a paged resource using POST with a application/x-www-form-urlencoded body, the response info SHOULD include a oslc:PostBody and the client SHOULD fetch that next page using POST with a www-form-urlencoded body read from the oslc:postBody.

      https://issues.oasis-open.org/browse/OSLCCORE-124 describes a proposal that POST with application/x-www-form-urlencoded body should be supported to avoid hitting URI length limits. OSLC paging described in http://open-services.net/bin/view/Main/OslcCoreSpecification#Resource_Paging describes how an oslc:ResponseInfo should include an oslc:nextPage link and that a client fetches the next page with a GET. However, requests, especially those for query, are likely to contain query parameters with long values such that URI length limits are broken. For paged query results, getting a page of results is more likely to exceed URI length limits as a stateless implementation will have to include additional parameter(s).

            Assignee:
            James Amsden (Inactive)
            Reporter:
            davidhoney
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: