I think it depends on how you define a stateless cacheable resource. I would like someone to clearly and explicitly demonstrate how a web URL with a query string does not have these RESTful properties.
e.g. http://en.wikipedia.org/wiki/Representational_State_Transfer "One can argue that any sufficiently rich command line interface can be considered "ReSTful" ... in that a fully qualified command line and set of switches/options and arguments can access any accessible application state. A web URL with query string is effectively a sort of command line with arguments." On Oct 23, 3:27 pm, "Carl Nobile" <[EMAIL PROTECTED]> wrote: > Actually no, that would not be REST if you do everything from one URL. You > need to read RESTful Web Services by Leonard Richardson & Sam Ruby ISBN: > 978-0-596-52926-0. This book has become the RESTful bible. Also read > RFC-2616 (http://www.faqs.org/rfcs/rfc2616.html) the HTTP 1.1 standard > document it explains the use of the HTTP methods, DELETE, GET, HEAD, OPTION, > POST, and PUT. There are two more but are not used in REST. You will also > be using a lot more status codes besides 200, 404, 500. > > -Carl > > > > On Thu, Oct 23, 2008 at 3:11 PM, wmiller <[EMAIL PROTECTED]> wrote: > > > On Oct 23, 12:15 pm, "Carl Nobile" <[EMAIL PROTECTED]> wrote: > > > If you're doing REST, which is what I do, you need to keep in mind that > > REST > > > is very URI intensive. Trying to define all of them in apache config > > files > > > is an impossible task. Remember these are URIs not URLs. URIs point to a > > > virtual object not a physical one and with a large database you can have > > > millions of them. Trying to do these in apache even using REGEX and > > rewrite > > > rules will never be as dynamically able to handle the number of URIs you > > > could have in a REST web service, doing it in code is a much more robust > > way > > > to do it. > > > > If you are really mapping files to URLs then maybe REST isn't what you > > need. > > > > -Carl > > > why do they have to be mutually exclusive? A single physical html > > file can have RESTful properties and serve as a basis for looking up > > many items in a database: > > >http://example.com/index.html?order_no=4 > > > The above has all the qualities of being RESTful. It points to a > > stateless resource and it's cacheable. > > -- > --------------------------------------------------------------------------- > ---- > Carl J. Nobile (Software Engineer) > [EMAIL PROTECTED] > --------------------------------------------------------------------------- > ---- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to modwsgi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en -~----------~----~----~----~------~----~------~--~---
