Austin Bonander

That's more of a Hyper limitation actually. Fortunately it's pretty simple to fix up, you just have to construct a `hyper::Client` with a TLS-capable Connector. `hyper-native-tls` seems to be the...

Then you would use [`anterofit::net::RawResponse`](https://docs.rs/anterofit/0.1.1/anterofit/net/response/struct.Raw.html) as your service method return type: ```rust fn create_comment_by_url(&self, link: &str, subject: &str, content: &str) -> RawResponse { POST("{}", link); fields! { "ws.op" => "createComment",...

However, if you want to abstract over this within the service definition alone, I don't really have anything for that yet. I've been conceptualizing a sort of `map_response!{}` macro, but...

The goal is to be able to abstract a lot of the weirdness inside the service definition but I'm not completely sure how I want to do that.

Yeah, it's in the works along with #6. I'm still working on https://github.com/abonander/multipart-async though.

On which project?

Yeah, if you want an upgrade of Serde now feel free to try it. I was thinking I'd lump all these changes into one release but it doesn't have to...

I intended this use-case to be handled via wrapping the return type of the service method with [`net::response::TryWithRaw`](https://docs.rs/anterofit/0.1.1/anterofit/net/response/struct.TryWithRaw.html) which will give the raw Hyper response including status code and headers....

I've got kind-of a plan to support this. On the `parse-generics` branch, I'm experimenting with a syntax for forcing a full return type using `-!>` instead of `->`, and then...

So currently, when you define a service method and declare some return type `T`, it gets rewritten as `Request`: ```rust service! { pub trait MyService { fn get_api_version(&self) -> String...