noPollConn* nopoll_conn_new_opts ( noPollCtx ctx,
noPollConnOpts opts,
const char *  host_ip,
const char *  host_port,
const char *  host_name,
const char *  get_url,
const char *  protocols,
const char *  origin 

Creates a new Websocket connection to the provided destination, physically located at host_ip and host_port and allowing to provide a noPollConnOpts object.

See nopoll_conn_new for more information.

ctxThe noPoll context to which this new connection will be associated.
optsThe connection options to use during the connection and the usage of this connection.
host_ipThe websocket server address to connect to.
host_portThe websocket server port to connect to. If NULL is provided, port 80 is used.
host_nameThis is the Host: header value that will be sent. This header is used by the websocket server to activate the right virtual host configuration. If null is provided, Host: will use host_ip value.
get_urlAs part of the websocket handshake, an url is passed to the remote server inside a GET method. This parameter allows to configure this. If NULL is provided, then / will be used.
originWebsocket origin to be notified to the server.
protocolsOptional protocols requested to be activated for this connection (an string of list of strings separated by a white space). If the server accepts the connection you can use nopoll_conn_get_accepted_protocol to get the protocol accepted by the server.
A reference to the connection created or NULL if it fails. Keep in mind the connection reported may not be connected at the time is returned by this function. You can use nopoll_conn_is_ready and nopoll_conn_is_ok to ensure it can be used. There is also a helper function (NOTE it is blocking) that can help you implement a very simple wait until ready operation: nopoll_conn_wait_until_connection_ready (however, it is not recommended for any serious, non-command line programming).

References nopoll_false, and NOPOLL_TRANSPORT_IPV4.