Remove constraint that request body is hyper::Body

[mitchhentges]

Thanks for Routerify! It's very useful for my hyper projects :)

I'm writing an application that acts as a small web container, and the service I'm using has an API that only uses the http crate's abstractions (rather than being specific to hyper).
However, this means that I can't use routerify, because it expects requests to be Request<hyper::Body> (as opposed to Request<&[u8]>, which the service provides).

Would it be possible to relax the constraint so that routes do Request<B> -> Response<B> instead?

[rousan]

Hey @mitchhentges, At the beginning I restricted to use hyper::Body as the base body type for simple design, but as the hyper crate accepts any body type as long as it implements HttpBody trait, so we can also restrict this trait constraint to routerify. We can have a plan to extend this in future.