On Oct 26, 2006, at 1:02 PM, Jan Algermissen wrote:
This is an interesting assertion about REST. I don't yet agree with it as stated though I might after further discussion and elaboration. To provide a possible counter-example, I always found the HTTP SEARCH proposal <http://www.greenbytes.de/tech/webdav/draft-reschke-webdav-search-latest.html> to be RESTful because - The results of a search are returned as a set of resource identifiers - It doesn't necessarily break for dynamic resources as long as the server can handle that - It doesn't break the layering of representations, or use of connectors, or caching of resources - It's general -- can be used for WebDAV resources but also for any HTTP server, CalDAV resources or probably (with some thought) Atom resources A server that instead provides light-weight query interfaces as you describe, or guides the client into the content, does not work with a client that doesn't do HTML (a CalDAV, WebDAV or possibly Atom authoring client); correct? Lisa |
- Adding POST capability to atom:link Gopalan Sri
- Re: Adding POST capability to atom:link Thomas Broyer
- Re: Adding POST capability to atom:link James M Snell
- Re: Adding POST capability to atom:link Jan Algermissen
- Re: Adding POST capability to atom:link A. Pagaltzis
- Re: Adding POST capability to atom:link Jan Algermissen
- Re: Adding POST capability to atom:link Jan Algermissen
- RE: Adding POST capability to atom:link Gopalan Sri
- Re: Adding POST capability to atom:link Jan Algermissen
- How to do RESTful SEARCH (was Re: Adding... Lisa Dusseault
- Re: How to do RESTful SEARCH (was R... Ernest Prabhakar
- Re: How to do RESTful SEARCH (was R... Jan Algermissen
- Re: How to do RESTful SEARCH (was R... Mark Baker
- Re: Adding POST capability to atom:link Thomas Broyer
- searches - was Re: Adding POST capability to atom:li... Henry Story
- Re: searches - was Re: Adding POST capability to... Jan Algermissen
- Re: searches - was Re: Adding POST capabilit... Henry Story