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

Test socket hangups #76

Closed
strk opened this issue Jun 14, 2013 · 2 comments
Closed

Test socket hangups #76

strk opened this issue Jun 14, 2013 · 2 comments
Labels
performance

Comments

@strk
Copy link
Contributor

strk commented Jun 14, 2013

I don't know what happens when requests get aborted on the client side.
Supposedly the server should be notified about that (with a socket hangup?) but I don't think we're handling that in any way. Ideally we should avoid doing useless work. What's useful and what not may not be straightforward in that we queue some request responses while waiting for the renderer cache to render a whole metatile, but this is definitely something we should look into.
@ghost ghost assigned strk Jun 14, 2013
@strk
Copy link
Contributor Author

strk commented Jan 30, 2014

Same thing for http timeout server side

@strk strk mentioned this issue Jan 30, 2014
Closed
@strk strk mentioned this issue Mar 20, 2014
Open
@strk strk added this to the 0.21.0 milestone Mar 20, 2014
@strk strk modified the milestones: 0.22.0, 0.21.0 Jun 18, 2014
@rochoa rochoa removed this from the 0.22.0 milestone Aug 19, 2014
@strk strk removed their assignment Aug 19, 2014
@rochoa
Copy link
Contributor

rochoa commented Jun 25, 2015

This should be addressed in #176

@rochoa rochoa closed this as completed Jun 25, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
performance
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rochoa @strk