Sergii Glushchenko

I think this can be implemented in a pre middleware similar to how warp does it https://github.com/seanmonstar/warp/blob/master/src/filters/body.rs#L51 Hyper will not read more than content-length bytes of the body.

@rousan If I understand you correctly, we already have ```rust /// The error type used by the error handlers. pub type RouteError = Box

> We have two error types right now, `routerify::Error` and `routerify::RouteError` and the `routerify::Result` is based on `routerify::RouteError` and it is very confusing. I agree. In retrospect, I should have...

Hyper uses a combination of both https://docs.rs/hyper/0.14.10/src/hyper/error.rs.html#11-13. There's still a way to get to the original boxed error. In general, I am not against a more structured error via enum....

@rousan did you mean the `keywords` section in Cargo.toml files?

Oh yeah, we actually use `hyper-tungstenite` at work too. The beauty of playing nicely with hyper is that so much is available out of the box. @rousan would you be...

Hey @ErwanDL, thanks for helping out with this! I personally do not have much time working on `routerify-websocket`, and given that `hyper-tungstenite` works just fine, my preference would be to...

> Oh okay, I had not understood that the idea was to remove completely the query middleware and just put its functionality in `RequestExt/PartsExt`, but that sounds like a good...

If nobody is working on this then I'd like to give it a try. After a quick look into the spec and the Go client, it seems that the first...

@nadenf thanks for the PR! Let's get `async-pipe-rs` sorted first and release a new version, then we can update the dependency here merge it and make a new release.