This page has three main sections. (Note that the listings could be empty.) more… Tip: Remember the back-button! And don't click the number on the left.

  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.
2266 ↑ ... is defined by > urn:BALL:managed
3655 see also >

What Is Time?

This is a short summary from Askemos.

We have to distinguish three kinds of time, when reasoning about global interpreters sharing data:

Wall Clock Time

Wall clock time is what we understand as the current date. is a hypothetical thing. In reality only a clock approximately synchronized to a universal time base is possible.

Node Time

Node time is whatever the clock the machine yields. Nodes need a reasonable synchronized clock, therefore NTP-synchronization is among the system requirements. Node time is available from SRFI 19 current-time and current-date. Note: node time is not useful for time values stored during transactions. Use process time for that!

Process Time

Process time is the time at which a transaction (see Mutating operation) appears to be performed eventually. It is attached to each message and agreed upon the quorum. (Similar to "official" processes, which often depend of the postmark for time measurement.) To access the virtual time in BAIL use message-date current-message().

2267 is a > BAIL procedure

created Property Accessor Name