Jump to: navigation, search

cometd Section



     


heartBeatTimeout

Default Value: 0
Valid Values: Any positive integer
Changes Take Effect: Immediately


Maximum number of seconds that the cometD connection can remain inactive before the server considers the client (browser) to be inactive. Note: "Ping" packets are not considered as activity-related.

This option is used when configuring the CometD Activity Extension (see https://docs.cometd.org/current/reference/#_extensions_activity).

interval

Default Value: 0
Valid Values: positive integer
Changes Take Effect: After server restart


The maximum number of seconds that the client must wait between the end of one long poll request and the start of the next. Corresponds to standard CometD interval option: http://cometd.org/documentation/cometd-java/server/configuration.

maxInterval

Default Value: 15
Valid Values: positive integer
Changes Take Effect: After server restart


The maximum number of seconds that the server will wait for a new long poll from a client before that client is considered invalid and is removed. Corresponds to the standard CometD maxInterval option: http://cometd.org/documentation/cometd-java/server/configuration.

maxSessionsPerBrowser

Default Value: 1
Valid Values:
Changes Take Effect: After server restart


Maximum count of CometD connections opened per browser connection.

timeout

Default Value: 30
Valid Values: positive integer
Changes Take Effect: After server restart


The maximum number of seconds that the server will wait for a message before responding to a long poll with an empty response. Corresponds to the standard CometD timeout option: http://cometd.org/documentation/cometd-java/server/configuration.

transports

Default Value: org.cometd.websocket.server.JettyWebSocketTransport, org.cometd.server.transport.JSONTransport, org.cometd.server.transport.JSONPTransport
Valid Values: comma-separated names of classes which implement CometD transport
Changes Take Effect: After server restart


Comma-separated list of allowed CometD transports. By default, all transports are supported. This option is useful if, for example, you need to to turn off the websocket transport on the server side.

This page was last edited on March 21, 2018, at 22:06.
Comments or questions about this documentation? Contact us for support!