[cap-talk] Webkeys vs. the web

[David-Sarah Hopwood]

Chip Morningstar wrote:
> "Stiegler, Marc D" <marc.d.stiegler at hp.com> wrote:
> 
>>>> This is more or less the approach I've been trying to follow, except 
>>>> that the SCoopFS UI is done using Flash and I'd like to just use straight
>>>> HTML+Javascript.  One advantage Flash has (I think) is that it has 
>>>> authority to squirrel bits away persistently, which allows it to hold 
>>>> onto capabilities across context switches.  I don't know if Alan was 
>>>> making use of any such thing, though.
>>>
>>> The local waterken server provides the persistent storage for SCoopFS.
>>
>> Or, more generally, a waterken server (local or remote) provides persistent
>> memory of where you left off. It provides this memory so reliably it is kinda
>> hard to start anywhere other than where you left off. Regardless, neither
>> alan's ui in flash nor my ui for the same system in javascript has ever had to
>> worry about remembering something in the browser. Indeed, one of the amusing
>> consequences of waterken is, you pick up where you left off even when you go
>> to a new browser, as long as you take the bookmark with you :-)
> 
> You guys, always with the bookmarks.

This is just working the way that the web is supposed to work: an URL
stably refers (when dereferenced using GET) to a resource. Therefore, a
bookmark stably refers to a resource. This doesn't mean you *have* to
use bookmarks; it means that when you use bookmarks, they do the
Right Thing (TM).

-- 
David-Sarah Hopwood ⚥