[Home] [By Thread] [By Date] [Recent Entries]


Liam Quin scripsit:

> I don't see why not, although the URLs might get a bit long if they
> had to keep the ISBNs for everything you've seen recently as well
> as for everything in your shopping cart.  

REST imposes no such requirement.  There is no problem with servers
keeping state; it's just that the state has to be expressed as a
hyperdocument which can be retrieved by presenting an appropriate URI
(plus appropriate security credentials as needed).

Having a page called "Liam Quin's Recent Purchases" with an URL like
http://store.example.com/recent/liamquinn32 is no problem; you would
have to present your credentials to view this page, since its contents
are sensitive.  Presumably it would contain links to pages with titles
like "Liam Quinn's 2004-01-01 Purchase of _The Complete Works of Leon
Trotsky_", which in turn would provide a link to the page for the
Complete Works.  It is the latter (unsecured) you would normally link to.

-- 
"No, John.  I want formats that are actually       John Cowan
useful, rather than over-featured megaliths that   http://www.ccil.org/~cowan
address all questions by piling on ridiculous      http://www.reutershealth.com
internal links in forms which are hideously        jcowan@r...
over-complex." --Simon St. Laurent on xml-dev

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member