Bob La Quey wrote:
You seem to be confusing REST with caching among other things. Caching
!= REST though REST often enhances caching.
Oh, and describe for me the URI that represents "Decrement Fred's
account by $100, and give $50 to Sally and $50 to whoever Sally names in
her configuration record, all in one transaction."
Or the URI that represents "Lock my mailbox against writing until I'm
done reading my mail and I have decided what to delete and what to
keep." Don't forget to unlock it if, for some reason, I finish without
unlocking it.
Or the URI that represents my ssh session to the server over there.
No, really, not everything is REST, and not everything can be
represented as one independent round trip to a server and back. There
really is state in the world. :-)
--
Darren New / San Diego, CA, USA (PST)
--
KPLUG-LPSG@kernel-panic.org
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
