On 26.10.2006, at 21:31, Gopalan Sri wrote:
Thank you all for your quick response. I apologize for the weak description of my problem.
Jan, you are correct in your assessment that I wish to parameterize my request to go to the next page because my parameters are too complex to represent in a query string.
If you aim to provide a REST interface, do not mimick a query interface (at least not a complex one). Think of your 'asset space' in terms of pre-defined, useful collections that you expose as resources (feeds) and provide light weight query interfaces to them that fit with GET requests.
Think in terms of browsing and drilling-down; REST interfaces guide the client into the content instead of assuming the knowledge to construct
a query does reside in the client.
This, BTW, avoids coupling your clients to the local data model specifics.
"The Web doesn’t do generic query"
Currently, we are representing our parameter in XML. The reasoning behind this is that we are trying to support an enterprise search operation using a SOAP and REST interfaces. Since we have to encode the request in XML for the SOAP interface, we were hoping to reuse that XML object within our REST based interfaces as well.
We are using Atom to capture the results of enterprise search. The problem I encounter arises when we start thinking about the paging of results. For RESTful access to our services, we are trying to use open source/commercial Atom readers that support Open Search. The recommendations laid out by the OpenSearch 1.1 specification (http://www.opensearch.org/Specifications/OpenSearch/1.1#Example_of_OpenSearch_response_elements_in_Atom_1.0) suggest implementing paging with <atom:link/> elements using specific values for @rel (e.g. self, first, previous, next, last). Right now I am trying to figure out how I can still follow their guidance while managing the fact that my parameter cannot easily be encoded as a regular query string.
Any thoughts would be appreciated. Thanks for your time.
On 26.10.2006, at 18:24, Gopalan Sri wrote:
something like this:
<link rel="next" href=""http://example.com">http://example.com/" type="application/atom+xml"
<parameter name="blah" value="blah"/>
If I understand this correctly, you intent to parameterize the request to go to the next page; since your parameters
seem to be too complex to but them into the query string, you thought about using POST - yes?
If so, this is bad practice anyhow, since you loose all the benefits of GET.