> I may want to start a cart today, add items tomorrow and
> place the order in a month.
> There's nothing in the REST architecture that says that I need to do
> everything in "one shot" by storing all this info in the client first.
> If I can get a resource identifier from the server, as I described
> earlier, I should be able to refer to it in the future.
Yes you certainly *can* do that, but still I don't see why you *want* to
store the cart on the server (the client could store it on it's HDD without
bothering the server, which is much more scalable as millions of clients
could keep their stuff for months, without a single bit stored on the
server), but anyways, let's close the thread, as it leads to nowhere.