[cap-talk] Persistence as a cap value (was: Re: ...PLASH discussion)

[Kevin Reid]

On Mar 13, 2008, at 13:07, Jonathan S. Shapiro wrote:

> The reason that a session is insecure following restart is that the
> publisher can no longer know who is sending packets from the other end
...
> When this happens, there is either a mechanism to re-construct and
> re-authenticate the session that existed between the machines, or more
> commonly there is not. The need to reconstruct is actually good,  
> because
> the applications on the respective sides are no longer mutually
> consistent following a failure.

I understand now.

(This is what E does; eventual refs are ephemeral and sturdy refs are  
persistent. However, the objects referred to by eventual refs may be  
persistent.)

-- 
Kevin Reid                            <http://homepage.mac.com/kpreid/>