Authentication information for the underlying connector
The authentication endpoint
Defines how the authentication endpoint, defined using authEndpoint, will be called. There are two options available: ajax and jsonp.
If you need custom authorization behavior you can provide your own authorizer function as follows:
A pusher client instance to use
Allows connecting to a different datacenter by setting up correct hostnames and ports for the connection.
The application CSRF token
Disables stats collection, so that connection metrics are not submitted to Pusher’s servers. These stats are used for internal monitoring only and they do not affect the account stats.
Specified which transports must not be used by Pusher to establish a connection. This settings overwrites transports whitelisted via the enabledTransports options. Available transports: ws, wss, xhr_streaming, xhr_polling, sockjs. Additional transports may be added in the future and without adding them to this list, they will be enabled.
Specifies which transports should be used by Pusher to establish a connection. Useful for applications running in controlled, well-behaving environments. Available transports: ws, wss, xhr_streaming, xhr_polling, sockjs. Additional transports may be added in the future and without adding them to this list, they will be disabled.
Forces the connection to use encrypted transports.
The pusher host to connect to
Ignores null origin checks for HTTP fallbacks. Use with care, it should be disabled only if necessary (i.e. PhoneGap).
The pusher auth key
The namespace to use for events
Time before the connection is terminated after sending a ping message. Default is 30000 (30s). Low values will cause false disconnections, if latency is high.
After this time (in miliseconds) without any messages received from the server, a ping message will be sent to check if the connection is still working. Default value is is supplied by the server, low values will result in unnecessary traffic.