Adam Hopkins

@LittleLampLight It does sound like something that should not be too difficult to add. Take a look at https://github.com/huge-success/sanic/blob/master/sanic/server.py, and you will see that `connections` currently are handled as a...

Correct, that is intentional. Out of curiosity, what is the use case that you are after with dispatching once before and after middleware? Is it to have control over when...

Actually, I think better than `http.middleware.before_all` would be `http.lifecycle.body` that executes here after reading the body. 

We should probably also include a lifecycle diagram in the docs with the flow of handlers, middleware, and signals.

The other thing about `CancelledError` that would be nice to avoid (if possible) is that it trips a lot of people up when they think they can catch it with...

...

May be impacted by: https://github.com/sanic-org/sanic/pull/2513

You make a good point. I think the core of what I was going after is the "gotcha" of a newcomer. This can easily be added with the new `Sanic.serve`...

That I think would cause more confusion. Currently: --dev == --debug + --auto_reload For debug mode to then change one thing would be non-obvious.

Okay, so I have put some more thoughts and effort into this. I think that we should perform the following: - `Sanic.serve` (and therefore also the `sanic` CLI) will *always*...