Support multiple http backends about oauth2-rs HOT 3 CLOSED

Thanks for filing this issue! If the use case is to support actors, then maybe the async requirement (#44) is more crucial here than the choice of HTTP client library. If we expose an async interface that returns a Future, that seems like something that could be integrated with the actor model, regardless of how the underlying outbound HTTP requests are made.

I'm still in favor of providing an interface for customizing the HTTP backend (mainly to allow callers to specify TLS parameters, proxies, etc.), but I'm not sure if that would necessarily help integrating with something like actix-web. In particular, the hyper::client::connect::Connect trait is quite low-level (bytes sent/received), while something actor-related probably operates at a higher level of abstraction (e.g., HTTP requests/responses).

from oauth2-rs.

Actix also supports Sync Actors, so it is not that crucial.

It's probably more an ideal (that is not necessary) to have everything done using actix. But I think a pure rust solution (like hyper) that does not depend on curl would be a better default.

from oauth2-rs.

multiple clients are supported in the latest master

from oauth2-rs.