Lists Home |
Date Index |
Gavin Thomas Nicol wrote:
> Continuations have a closure as well... in other words, typically, a
> continuation represents system state at a given point in time...
> typically by snapshotting the execution
Exactly. In fact some people do implement REST-style services using
continuations and closures. The URI is an index into the list of them.
> ... The terms here are
> interesting, because continuation and more importantly "closure" are
> the two terms that come explicitly to mind when I think of all the
> problems with HTTP, visibility, and open disclosure.
I don't know about you, but I don't have any concerns buying relatively
expensive plane tickets via HTTP. I haven't had any problem so far.
> > You don't need to send a pile of URIs. You send one. It refers to
> > the last state of our transaction.
> If this represents the last state of the application, what stops an
> intermediary (proxy) from using it and thereby spoofing the system?
You use a proxy because you want it to work on your behalf. Of course it
may spoof the system. So can your HTTP client. If you don't trust one of
them, you don't use it.