-
Notifications
You must be signed in to change notification settings - Fork 367
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
Concurrent Requests #268
Comments
Yes, we can probably remove that as it causes only issues. |
I beg to differ. Any application that uses request/ response abstraction and does internally not rely on state should be able to work with concurrent requests. One such example should be the volkszaehler middleware (https://github.com/volkszaehler/volkszaehler.org/blob/master/lib/Router.php) although it's not based on reactPHP. |
@andig Seems like that does blocking dispatching and thus can't support concurrent requests? |
See #302 for removing concurrent request support. |
@kelunik that is ... of course true. PR for removal is available. |
Currently there's a concurrent request feature, which kind of application really uses that? IMO applications that are able to concurrently process requests should directly use either
react/http
oramphp/aerys
, but do not benefit fromphp-pm/php-pm
.Should #267 be accepted, can we then remove that?
The text was updated successfully, but these errors were encountered: