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

Sockets refactor: allow any family/type/protocol association #3750

Merged
merged 3 commits into from
Dec 23, 2016

Commits on Dec 23, 2016

  1. Sockets refactor: allow any family/type/protocol association

    Refactor:
    
    - Socket is now enough to create, configure and use any kind of socket
      association of family, type and protocol is also possible, as long
      as it's supported by the underlying OS implementation.
    - The TCPSocket, TCPServer, UDPSocket, UNIXSocket and UNIXServer
      classes are merely sugar to avoid having to deal with socket details.
    - UNIXSocket and UNIXServer can now be used in DGRAM type, in addition
      to the default STREAM type.
    
    Features:
    
    - Adds Socket::Server type, included by both TCPServer and UNIXServer.
    - Adds Addrinfo DNS resolver, that wraps results from `getaddrinfo`.
    
    Breaking Changes:
    
    - IPAddress now automatically detects the address family, so the
      argument was removed (limited impact).
    ysbaddaden committed Dec 23, 2016
    Configuration menu
    Copy the full SHA
    d6c063a View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    afd3b2b View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    9b37ca3 View commit details
    Browse the repository at this point in the history