Launcher methodology

Whenever the Launcher detects a new event trigger, the watches associated with that trigger are either:

• initiated, thereby causing the map to execute
• placed in an initiation pending state, awaiting the completion of all specified triggers
• maintained in an initiation-pending state until operating system resources (such as threads) are available

The Launcher initiates an individual map thread for each successful combination of specified triggers. Multiple instances of the same map component can be invoked and executed simultaneously if the Launcher is configured to take advantage of concurrent multi-threading of map execution for performance. Alternatively, if strictly sequential execution architecture is required (FIFO); configuring the Launcher accordingly can accommodate this. This concurrent-versus-sequential capability can be configured at the individual map component level. As a result, maps contained in a system could be concurrent, while others could be set to execute sequentially.