Formalized Message Structure
Documenting the messages passed through the rpc layer to improve modularity and scalability.
Blueprint information
- Status:
- Complete
- Approver:
- Vish Ishaya
- Priority:
- Medium
- Drafter:
- Nova Upgrades Team
- Direction:
- Approved
- Assignee:
- Russell Bryant
- Definition:
- Approved
- Series goal:
- Accepted for folsom
- Implementation:
- Implemented
- Milestone target:
- 2012.2
- Started by
- Vish Ishaya
- Completed by
- Thierry Carrez
Related branches
Related bugs
Sprints
Whiteboard
At the very least, it would be helpful to somehow indicate (annotate?) the method calls that are intended to be called via RPC. -- Lorin
Also, what about using PyContracts <http://
Can't you find the functions being called by grep'ing for "rpc.call"?
Also would be nice to try out msgpack and see what performance gains we get. --tr3buchet
Since we have a blueprint for rpc versioning, this is blueprint is documenting the calls as they exist in version 1.
I think this blueprint is addressed by the patches proposed for https:/
QA:
----
Internal - coding/
Test Impact - None