1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162
//! Rust implementation of the Fizyr RPC procotol. //! //! The Fizyr RPC protocol is a request/response protocol, //! with bi-directional feedback as long as a request is open. //! Additionally, you can send individual stream messages that do not initiate a request. //! //! # Overview //! //! ## Peer and PeerHandle //! //! As a user of the library, you will mostly be using the [`PeerHandle`] object. //! The [`PeerHandle`] is used to interact with a remote peer. //! It is used to send and receive requests and stream messages. //! It can also be split in a [`PeerReadHandle`] and a [`PeerWriteHandle`], //! to allow moving the handles into different tasks. //! The write handle can also be cloned and used in multiple tasks. //! //! To obtain a [`PeerHandle`], you can call [`Peer::connect()`]. //! This will connect to a remote server and spawn a background task to read and write messages over the connection. //! If you need full control over tasks, you can instead create a [`Peer`] object //! and call [`Peer::run()`] manually. //! //! ## Server //! //! The [`Server`] struct is used to accept incoming connections //! and gives you a [`PeerHandle`] for each incoming connection. //! You can then use the handle to process incoming messages and to send messages to the peer. //! Usually, you will want to spawn a task for each accepted connection that handles the communication. //! //! ## Transports //! //! Each peer internally uses a [`Transport`][transport::Transport]. //! The transport is responsible for reading and writing raw messages. //! By abstracting away the message transport, //! the library can expose a single generic [`Peer`] and [`Server`] struct. //! //! There are different transports for different socket types. //! Different transports may also use different types as message body. //! For example, the [`TcpTransport`] and [`UnixStreamTransport`] //! use messages with a [`StreamBody`]. //! This [`StreamBody`] body type contains raw bytes. //! //! The [`UnixSeqpacketTransport`] has messages with a [`UnixBody`], //! which allows you to embed file descriptors with each message. //! //! # Features //! //! The library uses features to avoid unnecessarily large dependency trees. //! Each feature corresponds to a different transport type. //! None of the features are enabled by default. //! Currently, the library has these features: //! //! * `tcp`: for the [`TcpTransport`] //! * `unix-stream`: for the [`UnixStreamTransport`] //! * `unix-seqpacket`: for the [`UnixSeqpacketTransport`] //! //! # Example //! //! ```no_run //! use fizyr_rpc::{TcpPeer, StreamConfig}; //! //! # async fn foo() -> Result<(), Box<dyn std::error::Error>> { //! let mut peer = TcpPeer::connect("localhost:1337", StreamConfig::default()).await?; //! let mut request = peer.send_request(1, &b"Hello World!"[..]).await?; //! //! loop { //! let message = request.next_message().await?; //! let body = std::str::from_utf8(&message.body)?; //! //! if message.header.message_type.is_responder_update() { //! eprintln!("Received update: {}", body); //! } else if message.header.message_type.is_response() { //! eprintln!("Received response: {}", body); //! break; //! } //! } //! //! # Ok(()) //! # } //! ``` #![warn(missing_docs)] #[macro_use] mod macros; pub mod error; mod message; mod peer; mod peer_handle; mod request; mod request_tracker; mod server; pub mod transport; pub mod util; pub use message::service_id; pub use message::Body; pub use message::Message; pub use message::MessageHeader; pub use message::MessageType; pub use message::HEADER_LEN; pub use message::MAX_PAYLOAD_LEN; pub use peer::Peer; pub use peer_handle::PeerHandle; pub use peer_handle::PeerReadHandle; pub use peer_handle::PeerWriteHandle; pub use request::Incoming; pub use request::Outgoing; pub use request::ReceivedRequest; pub use request::SentRequest; pub use server::Server; pub use server::ServerListener; #[cfg(any(feature = "unix-stream", feature = "tcp"))] pub use transport::stream::StreamBody; #[cfg(any(feature = "unix-stream", feature = "tcp"))] pub use transport::stream::StreamConfig; #[cfg(feature = "unix-seqpacket")] pub use transport::unix::UnixBody; #[cfg(feature = "unix-seqpacket")] pub use transport::unix::UnixConfig; /// Message transport for TCP. #[cfg(feature = "tcp")] pub type TcpTransport = transport::StreamTransport<tokio::net::TcpStream>; /// Peer using the TCP transport. #[cfg(feature = "tcp")] pub type TcpPeer = Peer<TcpTransport>; /// Server for TCP sockets. #[cfg(feature = "tcp")] pub type TcpServer = Server<tokio::net::TcpListener>; /// Message transport for Unix stream sockets. #[cfg(feature = "unix-stream")] pub type UnixStreamTransport = transport::StreamTransport<tokio::net::UnixStream>; /// Peer using the Unix stream transport. #[cfg(feature = "unix-stream")] pub type UnixStreamPeer = Peer<UnixStreamTransport>; /// Server for Unix stream sockets. #[cfg(feature = "unix-stream")] pub type UnixStreamServer = Server<tokio::net::UnixListener>; /// Message transport for Unix seqpacket sockets. #[cfg(feature = "unix-seqpacket")] pub type UnixSeqpacketTransport = transport::UnixTransport<tokio_seqpacket::UnixSeqpacket>; /// Peer using the Unix seqpacket transport. #[cfg(feature = "unix-seqpacket")] pub type UnixSeqpacketPeer = Peer<UnixSeqpacketTransport>; /// Server for Unix seqpacket sockets. #[cfg(feature = "unix-seqpacket")] pub type UnixSeqpacketServer = Server<tokio_seqpacket::UnixSeqpacketListener>;