The Loci/Piper Project
ABSTRACT
INTRODUCTION
FOCUS & GOALS
DESIGN
BACKGROUND
CONTRIBUTORS
MAILING LISTS
DOCUMENTATION
SCREENSHOTS
DOWNLOAD
DESIGN
Piper has two subsystems, each containing two layers:- Build-Time Subsystem (BTS) (originally "The Loci Project")
- User Interfaces Layer (UIL) (see screenshots)
- Definitions Layer (DL)
- Run-Time Subsystem (RTS)
- Brokering Layer (BL) (originally "Generalized Messaging System" - GMS)
- Processing Layer (PL) (originally "Overflow" - part of FreeSpeech)
Below is an overview of the structure of the BL nodes that connect the DL to the PL. This configuration is realised during boot-up of the BL and will always be there. (Making it configurable or optional can be done, but it seems to be of no interest.)
Note that all the parts between the DL and PL on the drawing are one-and-the-same process, the BL. The sensors, visuals and collectors are dynamic loadable modules, that's why they are drawn seperately from the pipeline.
Also take notice of the way the communication between the DL and PL is set up. Communications back and forth go through the pipeline, so they are authorized, scheduled, etc. Also, the BL is designed so that the DL and PL do not need to be one the same machine. Neither do the other possible instances.
