-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What layer could we introduce an IP socket transport? #13
Comments
On Linux there is USB-over-IP :) On a more serious note I thought about attaching my Sweep to a Raspberry and using gRPC or serialization+communication combinations such as Protobuf / CapnProto + ZeroMQ / Nanomsg. Providing a stable |
See #12, #13. References: - http://api.zeromq.org/2-1:zmq-cpp
See #12, #13. References: - http://api.zeromq.org/2-1:zmq-cpp
See #12, #13. References: - http://api.zeromq.org/2-1:zmq-cpp
See #12, #13. References: - http://api.zeromq.org/2-1:zmq-cpp
In #47 I added an example using ZeroMQ and Protobuf for a pub/sub setup. Is this good enough or should we bring this out of the examples and into the main What are the requirements here, what do we actually need? |
Closing as not actionable on our side. Examples are there, we could install the publisher and subscriber, in addition to the proto scheme if needs be. |
Several applications are going to require communicating with sweep over IP. What layer of the SDK would be most appropriate to introduce this functionality?
The text was updated successfully, but these errors were encountered: