Version worker <-> engine messages

Registered by Joshua Harlow on 2014-06-08

To ensure that we can modify the message format in the future, we need to ensure that any messages sent from worker <-> engine (or vice-versa) have a version number associated with them (or in the envelope surronding the message). This will allow us to move from something like json to something else (msgpack for example) if we ever desire to in the future (for performance benefits or for schema benefits for example...)

Blueprint information

Status:
Not started
Approver:
None
Priority:
Medium
Drafter:
Joshua Harlow
Direction:
Approved
Assignee:
None
Definition:
Approved
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.