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

Introduce "softMaxInterval" #882

sbordet opened this issue Oct 29, 2019 · 0 comments

Introduce "softMaxInterval" #882

sbordet opened this issue Oct 29, 2019 · 0 comments


Copy link

@sbordet sbordet commented Oct 29, 2019

Option maxInterval controls the session expiration.

There are cases where it would be useful to detect when a client has connectivity problems and schedule some action - for example forfeit a game in 10 seconds.
If the connectivity is restored, the action can be canceled.

The idea is to have a softMaxInterval that triggers an event when the server does not receive a /meta/connect from the client, but before the ServerSession is expired by maxInterval.
Another event could be triggered when the server receives the /meta/connect before it expires.

Application could use these event to schedule their actions.

@sbordet sbordet added this to To do in CometD 5.0.0 via automation Oct 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
CometD 5.0.0
To do
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.