Class OutgoingConnectionBlueprint
java.lang.Object
org.apache.pekko.http.impl.engine.client.OutgoingConnectionBlueprint
INTERNAL API
-
Nested Class Summary
Nested ClassesModifier and TypeClassDescriptionstatic final class
This is essentially a three state state machine, it is either 'idle' - waiting for a response to come in or has seen the start of a response and is waiting for either chunks followed by MessageEnd if chunked or just MessageEnd in the case of a strict response.static final class
A merge that follows this logic: 1.static class
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionstatic org.apache.pekko.stream.scaladsl.BidiFlow<HttpRequest,
org.apache.pekko.stream.TLSProtocol.SslTlsOutbound, org.apache.pekko.stream.TLSProtocol.SslTlsInbound, HttpResponse, org.apache.pekko.NotUsed> apply
(Host hostHeader, ClientConnectionSettings settings, org.apache.pekko.event.LoggingAdapter log)
-
Constructor Details
-
OutgoingConnectionBlueprint
public OutgoingConnectionBlueprint()
-
-
Method Details
-
apply
public static org.apache.pekko.stream.scaladsl.BidiFlow<HttpRequest,org.apache.pekko.stream.TLSProtocol.SslTlsOutbound, applyorg.apache.pekko.stream.TLSProtocol.SslTlsInbound, HttpResponse, org.apache.pekko.NotUsed> (Host hostHeader, ClientConnectionSettings settings, org.apache.pekko.event.LoggingAdapter log)
-