Askemos

Help: This page shows how the referencing vocabulary definitions are maintained and interlinked for controlled consistency of documentation. Click on the hyperlinks to see how the terms are defined within the Askemos architecture. moreā€¦ Tip: Remember the back-button!

This page has three main sections. (Note that the listings could be empty.)

  1. The first item displays a term, URL, text or picture.
  2. Followed by a (still unordered) listing of statements about this subject. (for details follow ">"-link)
  3. Separated by a horizontal rule a "reverse" listing of statements referring to this item in object position.
Message (BALL implementation)
1300 is a > event
1304 description >

Message & Messages

A known source of confusion stems from the use of message for two distinct purposes. Especially technically skilled readers are prone to be trapped.

Messages at application level flow among application level objects. Invisibly to the application several physical nodes exchange a different kind of messages to synchronize their view of the application level.

App level messages are the only one, which carry (legal) meaning, are often transferred in memory, sometimes big and typically not written out to wire or disk. Messages exchanged during an update are what the technician think of: some short, cryptographically signed frame on the wire, which conveys check sums and version numbers to sync the nodes local state. App level messages in contrast are only considered and seen by the application when witnessed by the majority of hosts in "reasonable" synchrony.

1301 kind/genre/type > network transfer protocol