BALL

documentation

Concepts And Internals

Alternatives

Usage

  • TBD Howto and first steps.

    1. Semantics rest on unreliable, unidirectional message passing with share nothing semantics. This choice was inspired by and follows the motivation of the Erlang language. (However that's where the similarity to Erlang ends.)
    2. Separation of duties among the expression language BAIL and the CoreAPI is similliar to the relationship of Haskell and its IO monad.
  • Some agents (like this one) allow low level acces to their internal state. Try appending ?&xmlns=a to the URL. (Agent running the "hoist" code maintain manually limited history: following the links labled links and last-step reveals backup copies of former state.) Try this query to explore the SQL schema:

    ?mode=bail&xmlns=a&q=sql-query+"select+*+from+sqlite_master"

  • Core API to control effects

  • Capability based access control & incorruptibility

  • Applications may be written in any language. The core system supports:

  • TBD: Using WebDAV and mount directories via fuse

  • Monitoring

  • TBD: create a new peer (age old copy here)

  • Old manuals

Introductory Examples