Interface HttpClientTransport
- All Superinterfaces:
ClientConnectionFactory
- All Known Implementing Classes:
AbstractConnectorHttpClientTransport
,AbstractHttpClientTransport
,HttpClientTransportOverHTTP
HttpClientTransport
represents what transport implementations should provide
in order to plug-in a different transport for HttpClient
.
While the HttpClient
APIs define the HTTP semantic (request, response, headers, etc.)
how an HTTP exchange is carried over the network depends on implementations of this class.
The default implementation uses the HTTP protocol to carry over the network the HTTP exchange, but the HTTP exchange may also be carried using the FCGI protocol, the HTTP/2 protocol or, in future, other protocols.
-
Nested Class Summary
Nested classes/interfaces inherited from interface org.eclipse.jetty.io.ClientConnectionFactory
ClientConnectionFactory.Decorator
-
Field Summary
FieldsFields inherited from interface org.eclipse.jetty.io.ClientConnectionFactory
CONNECTOR_CONTEXT_KEY
-
Method Summary
Modifier and TypeMethodDescriptionvoid
connect
(InetSocketAddress address, Map<String, Object> context) Establishes a physical connection to the givenaddress
.newHttpDestination
(Origin origin) Creates a new, transport-specific,HttpDestination
object.void
void
setHttpClient
(HttpClient client) Sets theHttpClient
instance on this transport.Methods inherited from interface org.eclipse.jetty.io.ClientConnectionFactory
customize, newConnection
-
Field Details
-
HTTP_DESTINATION_CONTEXT_KEY
- See Also:
-
HTTP_CONNECTION_PROMISE_CONTEXT_KEY
- See Also:
-
-
Method Details
-
setHttpClient
Sets theHttpClient
instance on this transport.This is needed because of a chicken-egg problem: in order to create the
HttpClient
aHttpClientTransport
is needed, that therefore cannot have a reference yet to theHttpClient
.- Parameters:
client
- theHttpClient
that uses this transport.
-
newHttpDestination
Creates a new, transport-specific,HttpDestination
object.HttpDestination
controls the destination-connection cardinality: protocols like HTTP have 1-N cardinality, while multiplexed protocols like HTTP/2 have a 1-1 cardinality.- Parameters:
origin
- the destination origin- Returns:
- a new, transport-specific,
HttpDestination
object
-
connect
Establishes a physical connection to the givenaddress
.- Parameters:
address
- the address to connect tocontext
- the context information to establish the connection
-
getConnectionPoolFactory
ConnectionPool.Factory getConnectionPoolFactory()- Returns:
- the factory for ConnectionPool instances
-
setConnectionPoolFactory
- Parameters:
factory
- the factory for ConnectionPool instances
-