Difference between revisions of "Zaqar/specs/Protocols/Wire Transport"
< Zaqar
(Created page with "= Marconi ZMQ API: v1 Blueprint =") |
|||
Line 1: | Line 1: | ||
= Marconi ZMQ API: v1 Blueprint = | = Marconi ZMQ API: v1 Blueprint = | ||
+ | |||
+ | Since zmq is all about messages and there's no *defined* high level protocol, Marconi defined its own which tries to be as much compliant as possible with HTTP structure. | ||
+ | |||
+ | == Serialization == | ||
+ | |||
+ | Marconi's ZMQ transport uses either [http://msgpack.org/ messagepack] or [http://json.org/ json] as serialization format. It's recommended to use messagepack since it is faster and smaller than normal json. | ||
+ | |||
+ | == Structure == | ||
+ | |||
+ | <pre><nowiki> | ||
+ | { | ||
+ | header: { | ||
+ | }, | ||
+ | body: { | ||
+ | } | ||
+ | } | ||
+ | </nowiki></pre> | ||
+ | |||
+ | |||
+ | == Headers == |
Revision as of 08:55, 20 February 2013
Marconi ZMQ API: v1 Blueprint
Since zmq is all about messages and there's no *defined* high level protocol, Marconi defined its own which tries to be as much compliant as possible with HTTP structure.
Serialization
Marconi's ZMQ transport uses either messagepack or json as serialization format. It's recommended to use messagepack since it is faster and smaller than normal json.
Structure
{ header: { }, body: { } }