Flow-IPC 3.0.0
Flow-IPC project: Full implementation reference.
Classes | Namespaces | Functions
client_context.hpp File Reference
#include "ipc/transport/struc/shm/rpc/session_vat_network.hpp"
#include "ipc/transport/asio_local_stream_socket.hpp"
#include "ipc/session/app.hpp"
#include "ipc/common.hpp"
#include <flow/log/log.hpp>
#include <boost/make_shared.hpp>
#include <boost/shared_ptr.hpp>
#include <boost/thread/future.hpp>
#include <optional>
#include <algorithm>

Go to the source code of this file.

Classes

class  ipc::transport::struc::shm::rpc::Client_context< Client_session_t >
 An object of this type facilitates the establishment, in client style, of a zero-copy-enabled capnp-RPC conversation with an opposing process's Context_server. More...
 

Namespaces

namespace  ipc
 Catch-all namespace for the Flow-IPC project: A library/API in modern C++17 providing high-performance communication between processes.
 
namespace  ipc::transport
 Flow-IPC module providing transmission of structured messages and/or low-level blobs (and more) between pairs of processes.
 
namespace  ipc::transport::struc
 Sub-module of Flow-IPC module ipc::transport providing transmission of structured messages specifically.
 
namespace  ipc::transport::struc::shm
 Segregates zero-copy/SHM implementations of concepts residing in parent namespace ipc::transport::struc proper – most notably the concepts ipc::transport::struc::Struct_builder and ipc::transport::struc::Struct_reader – and items related to them.
 
namespace  ipc::transport::struc::shm::rpc
 Provides Flow-IPC's integration with Cap'n Proto's Remote Procedure Call (RPC) layer, wherein one can perform all the cool, promise-pipelined, interface-and-callback-happy RPC provided by capnp-RPC – while enjoying the zero-copy performance provided by Flow-IPC's SHM features.
 

Functions

template<typename Client_session_t >
std::ostream & ipc::transport::struc::shm::rpc::operator<< (std::ostream &os, const Client_context< Client_session_t > &val)
 Prints string representation of the given Client_context to the given ostream. More...