Event
An event is a dictionary. It contains any information the Connector decides to put into it.
The life cycle of an event:
- The Connector gets an event (a webpage hit, or an irc message for example)
- The Connector then builds a dict that contains all the information related to the event that plugins should get access to
- The Connector passes it to its EventHandler (provided by the Core)
- In the Core the event gets passed to the PluginManagers GetMatchingFunctions, and a list of (function,instance) that are listening for this event are returned.
- The event is extended with
"response":[[ResponseObject]], "self":instance- This is where a service could possibly add more?
- Each of the functions are paired with the event, and enqueued in the PluginDispatcher
- A PluginDispatcherWorkerThread pulls the (function,event) tuple off the queue
- Read PluginDispatcherWorkerThread to see what happens from this point on. The event is done with its life here.
None at the moment
