[cap-talk] A paper on web-keys

[Sandro Magi]

Toby Murray wrote:
> That's very cool -- not least because it takes advantage of the "the
> object's interface *is* the UI" idea that the Waterken approach makes
> possible. (Although I'm still yet to dig into the new JSON/JavaScript
> Waterken implementation but this certainly applies to the old XML/XSLT
> one.) I think that this is one of the key advantages that Waterken has
> over all other known capability implementations -- e.g. E, KeyKOS
> derivatives, etc.

The one concern I have about "the object is the UI" approach is upgrade.
Web applications are constantly being refactored, and upgrading a
persistent object store is a *tough* problem. It's my last unsolved
dilemma with the web-calculus, and there is little discussion of this in
the Waterken docs, so if someone has a solution, please let me know. I
think upgrade should be covered after the requisite "Hello World!".

Sandro