netty/netty — Issue #214: setReadable(false) does not take effect
Author: ngocdaothanh
Created: 2012-03-03 08:11:37+00:00
State: open

After seeing this critics:

```
Where problems come in is with pipe-lined requests, meaning a browser sends a bunch of requests in a big blast, then hangs out for all the responses. This was such a horrible stupid idea that pretty much everone gets it wrong and doesn’t support it fully, if at all. The reason is it’s much too easy to blast a server with a ton of request, wait a bit so they hit proxied backends, and then close the socket. The web server and the backends are now screwed having to handle these requests which will go nowhere.

Mongrel2 does not support pipe-lined requests. It sends one, and waits for the reponse, and if you want more, then tough.
```

I would like to make Xitrum (https://github.com/ngocdaothanh/xitrum) process request one by one. I use `setReadable(false)` to stop Netty from reading new requests. But it does not block new message from being passed to handlers.