RestClient
Related Docs:
object RestClient
| package client
You could argue that putting this here sullies the otherwise clean functional interface, but that sacrifice is laid upon the alter of sanity.
You could argue that putting this here sullies the otherwise clean functional interface, but that sacrifice is laid upon the alter of sanity. It's much easier to reason about which materializer/execution context is used when it comes baked in with a client -- in particular in the retry/failover scenarios.
We don't want to e.g. accidentally bring another materializer (and by extension its execution context) in scope from a stopped actor system
the materializer associated w/ this client
Does what it says on the tin -- send the HttpRequest and eventually return a HttpResponse.
Does what it says on the tin -- send the HttpRequest and eventually return a HttpResponse.
The client is presumably established for a know HostLocation, but
the request to send
the response in a future
See materializer comment
See materializer comment
the execution context associated w/ this client
Represents the client to a web service,