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

Fix connection lifetime semantics #2

Closed
6 tasks done
davidfowl opened this issue Oct 1, 2016 · 1 comment
Closed
6 tasks done

Fix connection lifetime semantics #2

davidfowl opened this issue Oct 1, 2016 · 1 comment

Comments

@davidfowl
Copy link
Owner

davidfowl commented Oct 1, 2016

  • Make sure things each of the transports disconnect when the browser is closed (http/javascript)
  • Make sure events happen in the right order (disconnect during a send, send after disconnect)
  • Handle server shutdown
  • Make sure all memory is released when:
    • The user code loop ends
    • The transport ends (client disconnects)
  • Per connection Timeouts - Long polling only
  • Server initiated disconnects.
@davidfowl
Copy link
Owner Author

Make sure things each of the transports disconnect when the browser is closed (http/javascript)

This doesn't work great because we can't detect client FIN when running on Kestrel. WebListener works though. If we don't write to the output the FIN from the server is never sent and the RequestAborted token never fires.

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

No branches or pull requests

1 participant