Creates a Tcp.ServerBinding instance which represents a prospective TCP server binding on the given endpoint
.
Creates a Tcp.ServerBinding instance which represents a prospective TCP server binding on the given endpoint
.
Please note that the startup of the server is asynchronous, i.e. after materializing the enclosing akka.stream.scaladsl.RunnableGraph the server is not immediately available. Only after the materialized future completes is the server ready to accept client connections.
The interface to listen on
The port to listen on
Controls the size of the connection backlog
TCP options for the connections, see akka.io.Tcp for details
Controls whether the connection is kept open even after writing has been completed to the accepted TCP connections. If set to true, the connection will implement the TCP half-close mechanism, allowing the client to write to the connection even after the server has finished writing. The TCP socket is only closed after both the client and server finished writing. If set to false, the connection will immediately closed once the server closes its write side, independently whether the client is still attempting to write. This setting is recommended for servers, and therefore it is the default setting.
Creates a Tcp.ServerBinding instance which represents a prospective TCP server binding on the given endpoint
handling the incoming connections using the provided Flow.
Creates a Tcp.ServerBinding instance which represents a prospective TCP server binding on the given endpoint
handling the incoming connections using the provided Flow.
Please note that the startup of the server is asynchronous, i.e. after materializing the enclosing akka.stream.scaladsl.RunnableGraph the server is not immediately available. Only after the returned future completes is the server ready to accept client connections.
A Flow that represents the server logic
The interface to listen on
The port to listen on
Controls the size of the connection backlog
TCP options for the connections, see akka.io.Tcp for details
Controls whether the connection is kept open even after writing has been completed to the accepted TCP connections. If set to true, the connection will implement the TCP half-close mechanism, allowing the client to write to the connection even after the server has finished writing. The TCP socket is only closed after both the client and server finished writing. If set to false, the connection will immediately closed once the server closes its write side, independently whether the client is still attempting to write. This setting is recommended for servers, and therefore it is the default setting.
Creates an Tcp.OutgoingConnection without specifying options.
Creates an Tcp.OutgoingConnection without specifying options. It represents a prospective TCP client connection to the given endpoint.
Note that the ByteString chunk boundaries are not retained across the network, to achieve application level chunks you have to introduce explicit framing in your streams, for example using the Framing stages.
Creates an Tcp.OutgoingConnection instance representing a prospective TCP client connection to the given endpoint.
Creates an Tcp.OutgoingConnection instance representing a prospective TCP client connection to the given endpoint.
Note that the ByteString chunk boundaries are not retained across the network, to achieve application level chunks you have to introduce explicit framing in your streams, for example using the Framing stages.
The remote address to connect to
Optional local address for the connection
TCP options for the connections, see akka.io.Tcp for details
Controls whether the connection is kept open even after writing has been completed to the accepted TCP connections. If set to true, the connection will implement the TCP half-close mechanism, allowing the server to write to the connection even after the client has finished writing. The TCP socket is only closed after both the client and server finished writing. This setting is recommended for clients and therefore it is the default setting. If set to false, the connection will immediately closed once the client closes its write side, independently whether the server is still attempting to write.