Skip to content
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

Problem: our types were too loose #55

Merged
merged 1 commit into from
Feb 15, 2016
Merged

Problem: our types were too loose #55

merged 1 commit into from
Feb 15, 2016

Conversation

taotetek
Copy link
Contributor

Solution: rework our socket types. This PR:

  • Adds a base ZeroMQSocket interface, along with a Client interface for sockets that act as clients (e.g. connect to things) and a Server interface for sockets that act as servers (e.g., bind).
  • Adds a ConnectClient function that accepts Client interfaces + an endpoint and attempts to connect the Client to the endpoint
  • Adds a BindServer function that accepts Bind interfaces and binds them to an endpoint
  • Adds a ClientSocket type that is a ZMQ_CLIENT socket implementing the Client interface
  • Adds a ServerSocket type that is a ZMQ_SERVER socket implementing the Server interface

There is still a lot of work to be done to support multiple connections between clients and servers but this lays the groundwork for a more sane type system to build upon.

hintjens added a commit that referenced this pull request Feb 15, 2016
Problem: our types were too loose
@hintjens hintjens merged commit 1cab7d3 into zeromq:master Feb 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants