-
Notifications
You must be signed in to change notification settings - Fork 18
Wrp
Weston Schmidt edited this page Dec 2, 2017
·
2 revisions
The XMiDT service is designed to be able to travel across different connection types (HTTP, Websocket, Nanomsg, etc) and subsequently needs a mechanism to collect all the details needed to deliver, process and respond to a request.
Check out the different pages about the different WRP messages.
When the WRP structure hits the wire it is encoded using MsgPack regardless of how the API caller specifies it (MsgPack, JSON or via HTTP headers). The XMiDT service converts the incoming requests into MsgPack and sends it along. This conversion is not free. It costs your request a bit of time to be converted, so if you're trying to squeeze out every las millisecond of performance think about emitting WRP as MsgPack directly.