Finish implementing Messaging system

[NixAshes]

Basic framework is in place.

TODO:

• [x] Implementation of specialty Message types - Security, Data requests, possibly Config, etc.
• [ ] Traffic control in brokers
• [ ] Implement Observer methods for all classes (rationale: this could be done anonymously through composition, but for readability, prefer to have defined instance methods implementing the interface for now)
• [x] Actually make a decision on whether to go with one-way anonymous traffic (where each Message may or may not result in a completely separate Message being sent back through the broker) vs. two-way traffic with promises (where a Message that needs a response provides a Promise to be resolved once the receiver is finished executing the Message request).
• [ ] Implementation of method(s) for outgoing Messages - creation and submission to broker

[NixAshes]

I think for now I'm going to split the determination on whether to go with the Promise resolution response type vs. Response message type based on the following:

• For calls that would be synchronous if the system were coupled more tightly, I'll use Promises - theoretically they should be able to be resolved very quickly and shouldn't introduce problems associated with async that way, but we get the traceability of the Promise.
• For calls that are naturally async - specifically DataRequests - I'll have a corresponding Response type that will bundle the original request with the result from the DB and be sent back through the Brokers. The response will still be wrapped in a Promise (both for typechecking and traceability) but should be able to be resolved immediately (I hope).

This is all highly theoretical for now and may very well have to be changed later, but hopefully this way we get a minimum of async issues and traceability. Should have more info later this weekend.

[jacklmbrt07]

Just finished implementing messageFactory.ts