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.

Sign up for GitHub

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

Jump to bottom

Why does not XHRTransportConnection implement timeouts, while Websocket do? #19

Open
SQReder opened this issue Nov 9, 2018 · 1 comment
Open

Why does not XHRTransportConnection implement timeouts, while Websocket do? #19

SQReder opened this issue Nov 9, 2018 · 1 comment

Comments

@SQReder
Copy link

SQReder commented Nov 9, 2018

It leads to memory leaks, because sessions which has not explicitly closed by client will never be wiped out.
@SQReder SQReder changed the title Why does not XHRTransportConnection implement timeouts? Why does not XHRTransportConnection implement timeouts like Websocket do? Nov 9, 2018
@SQReder SQReder changed the title Why does not XHRTransportConnection implement timeouts like Websocket do? Why does not XHRTransportConnection implement timeouts, while Websocket do? Nov 9, 2018
@SQReder
Copy link
Author

SQReder commented Jan 24, 2019

bump

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@SQReder