You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2014/07/18 03:19:36 UTC
[Bug 56740] New: suspended_count not maintained properly with
wstunnel
https://issues.apache.org/bugzilla/show_bug.cgi?id=56740
Bug ID: 56740
Summary: suspended_count not maintained properly with wstunnel
Product: Apache httpd-2
Version: 2.5-HEAD
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: mod_proxy_wstunnel
Assignee: bugs@httpd.apache.org
Reporter: covener@gmail.com
While we wait for our callback, suspended_count has been incremented. But just
receiving our callback does not decrement it, since event doesn't know what
we're doing.
The current/recent resume API assumes a resume means getting a socket ready for
the next HTTP request and would break us.
So i think another simpler resume API is needed for this case where some
timer/whatever callback can say they're again working on an active request for
th duration of the callback, then when if they do not finish (technically NOT
another suspend) they need yet another API to bump the count up again.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org