Compysition

- Changed CompysitionEvent to Event and subclassed types using XML, JSON, and Http mixins or subclasses.
- Changed paradigm to no longer pass string values, but to rather pass complete data object references with each event subclass. This will prevent a lot of conversions between actors
- Added input/output validation on actor queue connection for actor compatibility checks. Also added a runtime check to verify that an event is indeed the expected event class that the actor needs
| NOTE: At this time, automatic conversion attempt occurs, with a logged warning. *This may change to a full exception in the future*
- Enhanced wsgi.py to handle content-types in routes definition, returning a 415 if content type on an incoming request does not match configuration for that route
- Mapped wsgi.py content types to their corresponding event subclass (JSONHttpEvent for 'application/json', etc)
- Created many exceptions in compysition.errors for various programming states. This was based originally off http codes and
| statuses that were relevant to programmatic states, but I wanted to decouple code from assuming an event was HTTP-based. Hence, thrown exceptions
- Added an additional check for uncaught exceptions on Actor.consume execution that will automatically route an event to error queues
| if an uncaught exception occurs
- Added 'register_error_actor' that will connect itself to all actors that DO NOT HAVE explicit error queues connected already
- Renamed several actors to more appropriate names.
| wsgi.Wsgi -> httpserver.HTTPServer
| xmlmatcher.XMLMatcher -> eventjoin.EventJoin
| transformer.Transformer -> xslt.XSLT
| xmlvalidator.XMLValidator -> xsd.XSD
| zmqpushpull -> zeromq
| testevent.TestEvent -> eventgenerator.EventGenerator
| udpeventgenerator -> eventgenerator
| cookietest -> cookie
- Multiple docstring updates
- Several test cases for actor input/output written. Not yet entirely complete, but a good start


Version

- Changed project structure to be more in line with what this framework is. It is an actor based event loop. Calling actors modules causes terminology collision with pythonic modules, and is inaccurate. Changed all instances of 'module' terminology to 'actor'
- Added explicitness to some calls, most importantly 'connect' and 'connect_error', which are now 'connect_queue' and 'connect_error_queue' on Director, respectively
- Changed all uses of event to use the new CompysitionEvent object. event['header'] was converted to be now simply a reference to a set attribute on the CompysitionEvent object. e.g. event['data'] is now event.data and event['header']['meta_id'] is now event.meta_id, etc
- Removed 'data' and 'header' actors, in favor of "EventAttributeModifier" actor, which modifies an event with a static attribute value. It defaults to modifying the 'data' attribute. This single actor serves as the functionality for the old 'data' and 'header' actors, so they were removed
- Fixed some typos and bugs in the last dev version

Version

- Removed all list\_* methods from QueuePool. Use python dict iter tool to iterate over the queue pool values
- Removed all camel case method calls. More pythonic
- Added director and removed router, as the router does not actually have anything to do with routing beyond configuration. Director was more fitting with the project, and more aptly named
- Immense refactoring, multiple instances of using reference rather than calling getters
- Removed a lot of unused and overly complicated code
- Added prototype for standardized CompysitonEvent, as mentioned previously in my TODO in Actor.create_event, this is overdue and just makes sense. The best practice for ZeroMQ and interprocess serialization is still TBD
- Changed naming of Major Domo pieces to be more consistent
- Added MDP Example in README.rst

- Changed EventRouter to use the newly created 'queues' functionality of Actor.send_event. This fixed a bug where event references were passed uncopied to multiple queues, causing collision on event editing by multiple actors.
- Started using 'restartlet' for Actor.threads pool. All long-running greenlets spawned on actors from self.threads will auto restart on an exceptional exit.
- Removed legacy support for director.connect_queue() - strings in the format "modulename.outboxname" or "modulename.inboxname" will no longer be accepted

- Added the concept of the 'meta_id' to an event. This is designed to allow a newly generated event to be associated to the data flow of an event that was previously persisted outside of the immediate event data-flow. To summarize the proper uses of 'event_id' vs 'meta_id':
- event_id: Used for internal compysition operations. Should be unique and immutable for every event generated in compysition. Changing this value breaks certain control actors - it should not be altered once generated for a new event.
- meta_id: This is an ID that associates it with an overall meta work, such as a series of generated events that all pertain to the same 'theme' of work. For example, a form of some sort waiting for human approval in a database won't be a part of the active compysition dataflow, but for logging purposes we would want the new series of compysition events that follow that approval to log with an ID that allows us to easily associate the 'form creation' and the 'post approval' steps. For this, we have the meta_id. Logging invocations that pass the 'event' variable to the qlogger will always use meta_id over the event_id. **Changing this value has no effect on the internal workings of compysition actors. It is purely for logging associations**

- Added "create_event" method on the Actor class. This allows a uniform and standardized event creation syntax, rather than re-creating events and event dict syntaxes in multiple locations. This will be a precursor to implementing an Event() object - The reason it was not done at this time is because testing is required to ensure that serialization works flawlessly across ZeroMQ sockets

- Modified behavior of a MajorDomo Broker so that it issues a disconnect command to a worker that heartbeats after it has been deleted from the broker. This then triggers a re-registration between the worker and broker.