WebSockex v0.1.1 WebSockex.Conn
Handles establishing and controlling the TCP connection.
Dispatches to the correct module for the underlying connection. (:gen_tcp or :ssl)
Is woefully inadequite for verifying proper peers in SSL connections.
Summary
Functions
Builds the request to be sent along the newly opened socket
Closes the socket and returns the Conn map without the socket
Waits for the request response, decodes the packet, and returns the response headers
Returns a new WebSockex.Conn struct from a uri and options
Opens a socket to a uri and returns a conn struct
Sets the socket to active
Sends data using the conn_mod module
Waits for the server to close the connection
Types
connection_option :: {:extra_headers, [header]} | {:cacerts, [certification]} | {:insecure, boolean}
Functions
Builds the request to be sent along the newly opened socket.
The key parameter is part of the websocket handshake process.
Closes the socket and returns the Conn map without the socket.
When the :socket field is nil in the struct, the function just returns
the struct as is.
handle_response(WebSockex.Conn.t) :: {:ok, [header]} | {:error, reason :: term}
Waits for the request response, decodes the packet, and returns the response headers.
Sends any access information in the buffer back to the process as a message to be processed.
Returns a new WebSockex.Conn struct from a uri and options.
Opens a socket to a uri and returns a conn struct.
set_active(WebSockex.Conn.t, true | false) :: :ok | {:error, reason :: term}
Sets the socket to active.
Sends data using the conn_mod module.
wait_for_tcp_close(WebSockex.Conn.t, integer) :: WebSockex.Conn.t
Waits for the server to close the connection.
Returns the Connection without the socket.
The spec says the server should close the TCP connection and the client should wait. I don’t know how long we should wait but 5 seconds seems good.