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

Support for cometd custom client configuration #12

Open
uklance opened this issue Jun 18, 2012 · 1 comment
Open

Support for cometd custom client configuration #12

uklance opened this issue Jun 18, 2012 · 1 comment

Comments

@uklance
Copy link
Owner

uklance commented Jun 18, 2012

See options here

Parameter Name Required Default Value Parameter Description
url yes The URL of the Bayeux server this client will connect to.
logLevel no info The log level. Possible values are: "warn", "info", "debug". Output to window.console if available.
maxConnections no 2 The maximum number of connections used to connect to the Bayeux server. Change this value only if you know exactly the client's connection limit and what "request queued behind long poll" means.
backoffIncrement no 1000 The number of milliseconds that the backoff time increments every time a connection with the Bayeux server fails. CometD attempts to reconnect after the backoff time elapses.
maxBackoff no 60000 The maximum number of milliseconds of the backoff time after which the backoff time is not incremented further.
reverseIncomingExtensions no true Controls whether the incoming extensions are called in reverse order with respect to the registration order.
maxNetworkDelay no 10000 The maximum number of milliseconds to wait before considering a request to the Bayeux server failed.
requestHeaders no {} An object containing the request headers to be sent for every Bayeux request (for example, {"My-Custom-Header":"MyValue"}).
appendMessageTypeToURL no true Determines whether or not the Bayeux message type (handshake, connect, disconnect) is appended to the URL of the Bayeux server (see above).
autoBatch no false Determines whether multiple publishes that get queued are sent as a batch on the first occasion, without requiring explicit batching.
connectTimeout no 0 The maximum number of milliseconds to wait for a WebSocket connection to be opened. It does not apply to HTTP connections. A timeout value of 0 means to wait forever.
@uklance
Copy link
Owner Author

uklance commented Jun 19, 2012

Related to #15

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant