You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Weston Schmidt edited this page Dec 2, 2017
·
2 revisions
Why does XMiDT need WRP?
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.
How can I leverage them?
Check out the different pages about the different WRP messages.
Common themes
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.