I think Don's definition of Lo-Rest is, hmm.. to Lo' :) He doesn't specify anything about requests being stateless, idempotent (woo, big word!), and just about any significant rules of REST.
I posted a comment on the post along these lines. :DG< On 3/19/06, Dr. Ernie Prabhakar <[EMAIL PROTECTED]> wrote: > > I thought this was a very useful distinction. I find myself (as a > pragmatist) more drawn to Lo-REST, but I do feel guilty about not using > Hi-REST. At least now I have a name for what I feel guilty about. ;-) > > -- Ernie P. > > http://www.25hoursaday.com/weblog/PermaLink.aspx?guid=473cc14f-4668-43cf-b5b9-0178f9271296 > > http://pluralsight.com/blogs/dbox/archive/2006/03/18/20235.aspx > > > > To get a more accurate picture of what we've done so far, I'll break this > category in two: Lo-Rest, which is the use of HTTP GET (or equiv) for > information retrieval/query, and Hi-Rest, which is characterized by the use > of HTTP PUT and DELETE (or equiv) for doing update. > > > > _______________________________________________ > microformats-rest mailing list > [email protected] > http://microformats.org/mailman/listinfo/microformats-rest > > > _______________________________________________ microformats-rest mailing list [email protected] http://microformats.org/mailman/listinfo/microformats-rest
