60fb163331
* +doc #20192 explain need of draining entities in server/client HTTP * missing javadsl for Connection header * Update HttpClientExampleDocTest.java
35 lines
1.3 KiB
ReStructuredText
35 lines
1.3 KiB
ReStructuredText
.. _http-client-side:
|
|
|
|
Consuming HTTP-based Services (Client-Side)
|
|
===========================================
|
|
|
|
All client-side functionality of Akka HTTP, for consuming HTTP-based services offered by other endpoints, is currently
|
|
provided by the ``akka-http-core`` module.
|
|
|
|
It is recommended to first read the :ref:`implications-of-streaming-http-entities` section,
|
|
as it explains the underlying full-stack streaming concepts, which may be unexpected when coming
|
|
from a background with non-"streaming first" HTTP Clients.
|
|
|
|
Depending on your application's specific needs you can choose from three different API levels:
|
|
|
|
:ref:`connection-level-api`
|
|
for full-control over when HTTP connections are opened/closed and how requests are scheduled across them
|
|
|
|
:ref:`host-level-api`
|
|
for letting Akka HTTP manage a connection-pool to *one specific* host/port endpoint
|
|
|
|
:ref:`request-level-api`
|
|
for letting Akka HTTP perform all connection management
|
|
|
|
You can interact with different API levels at the same time and, independently of which API level you choose,
|
|
Akka HTTP will happily handle many thousand concurrent connections to a single or many different hosts.
|
|
|
|
|
|
.. toctree::
|
|
:maxdepth: 2
|
|
|
|
connection-level
|
|
host-level
|
|
request-level
|
|
client-https-support
|
|
websocket-support
|