Network I/O with Brokers¶
When communicating to other services in the network, sometimes low-level socket I/O is inevitable. For this reason, CAF provides brokers. A broker is an event-based actor running in the middleman that multiplexes socket I/O. It can maintain any number of acceptors and connections. Since the broker runs in the middleman, implementations should be careful to consume as little time as possible in message handlers. Brokers should outsource any considerable amount of work by spawning new actors or maintaining worker actors.
Note that all UDP-related functionality is still experimental.
Brokers are implemented as functions and are spawned by calling on of the three following member functions of the middleman.
template <spawn_options Os = no_spawn_options, class F = std::function<void(broker*)>, class... Ts> typename infer_handle_from_fun<F>::type spawn_broker(F fun, Ts&&... xs); template <spawn_options Os = no_spawn_options, class F = std::function<void(broker*)>, class... Ts> expected<typename infer_handle_from_fun<F>::type> spawn_client(F fun, const std::string& host, uint16_t port, Ts&&... xs); template <spawn_options Os = no_spawn_options, class F = std::function<void(broker*)>, class... Ts> expected<typename infer_handle_from_fun<F>::type> spawn_server(F fun, uint16_t port, Ts&&... xs);
spawn_broker simply spawns a broker. The convenience
spawn_client tries to connect to given host and port over
TCP and returns a broker managing this connection on success. Finally,
spawn_server opens a local TCP port and spawns a broker managing it
on success. There are no convenience functions spawn a UDP-based client or
void configure_read(connection_handle hdl, receive_policy::config config);
Modifies the receive policy for the connection identified by
This will cause the middleman to enqueue the next
according to the given
config created by
x denoting the
number of bytes).
void write(connection_handle hdl, size_t num_bytes, const void* buf) void write(datagram_handle hdl, size_t num_bytes, const void* buf)
Writes data to the output buffer.
void enqueue_datagram(datagram_handle hdl, std::vector<char> buf);
Enqueues a buffer to be sent as a datagram. Use of this function is encouraged
over write as it allows reuse of the buffer which can be returned to the broker
void flush(connection_handle hdl); void flush(datagram_handle hdl);
Sends the data from the output buffer.
template <class F, class... Ts> actor fork(F fun, connection_handle hdl, Ts&&... xs);
Spawns a new broker that takes ownership of a given connection.
Returns the number of open connections.
void close(connection_handle hdl); void close(accept_handle hdl); void close(datagram_handle hdl);
Closes the endpoint related to the handle.
expected<std::pair<accept_handle, uint16_t>> add_tcp_doorman(uint16_t port = 0, const char* in = nullptr, bool reuse_addr = false);
Creates new doorman that accepts incoming connections on a given port and returns the handle to the doorman and the port in use or an error.
expected<connection_handle> add_tcp_scribe(const std::string& host, uint16_t port);
Creates a new scribe to connect to host:port and returns handle to it or an error.
expected<std::pair<datagram_handle, uint16_t>> add_udp_datagram_servant(uint16_t port = 0, const char* in = nullptr, bool reuse_addr = false);
Creates a datagram servant to handle incoming datagrams on a given port. Returns the handle to the servant and the port in use or an error.
expected<datagram_handle> add_udp_datagram_servant(const std::string& host, uint16_t port);
Creates a datagram servant to send datagrams to host:port and returns a handle to it or an error.
Manually Triggering Events experimental¶
Brokers receive new events as
new_data_msg as soon and as often as they occur, per default. This
means a fast peer can overwhelm a broker by sending it data faster than the
broker can process it. In particular if the broker outsources work items to
other actors, because work items can accumulate in the mailboxes of the
x is a connection or
acceptor handle and
y is a positive integer, allows brokers to halt
y additional events. Once a connection or acceptor
stops accepting new data or connections, the broker receives a
Brokers can stop activities unconditionally with
resume activities unconditionally with