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
{{ message }}
This repository has been archived by the owner on Apr 22, 2018. It is now read-only.
Problem: Often, we want our protocol to have a control (which can be slow, but has to be very extensible and easy to understand) part and a fast binary (for data acquisitions, which must be fast, but can be more complex and not so extensible).
Currently, we use a simple framing protocol on top of Malamute which does both jobs not so well. We do the control part OK, but the acquisition part we must poll the server for completion.
Problem: Often, we want our protocol to have a control (which can be slow, but has to be very extensible and easy to understand) part and a fast binary (for data acquisitions, which must be fast, but can be more complex and not so extensible).
Currently, we use a simple framing protocol on top of Malamute which does both jobs not so well. We do the control part OK, but the acquisition part we must poll the server for completion.
Possible solution: Implement a REST protocol (http://hintjens.com/blog:86, http://rfc.zeromq.org/spec:40) for the control part and a On-Demand Streamed Data (https://github.com/zeromq/malamute/blob/master/MALAMUTE.md) for the data acquisition part.
The text was updated successfully, but these errors were encountered: