[cap-talk] Capability-based Projects - theory vs. practice

[Dean Tribble]

Additional  capability systems and/or efforts.  MarkM: please verify :)

I think that the FCP system (Flat Concurrent Prolog, by Udi Shapiro and the
Weizmann Institute) was a capability-based system. Janus and other
concurrent constraint systems by Vijay Saraswat in the FCP tradition were
also capability systems.

1986: Vulcan Project - Ken Kahn (and MarkM and me and others) @ Xerox PARC
An actor language layered on FCP.

Joule started in 1988 or early 1989.

ToonTalk, by Ken Kahn, is actually a capability system, in spite of being a
programming environment for children. I think it started around 1994.

1994: Corbamite - Agorics/SunLabs
This was a C++ system vaguely related to Corba, but using capabilities.  The
actual network security enforcement was never implemented, but the
components were all designed following that approach.  It was the second
attempt to apply Joule insights to a sequential programming system (Promises
in Xanadu was the first), and contributed a lot to later E designs.

1995: GuardOS - Agorics
This is/was a KeyKOS derivative for Sparc and eventually other platforms.
It got to the point of emulating enough Solaris to host Java and let us
experiment with running Agorics' Java applications on it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.eros-os.org/pipermail/cap-talk/attachments/20070811/7776428f/attachment.html