Implementing a unary, async server
In the first iteration, we will deal with a traditional RPC call; it takes one input argument and returns one output value.
Software & Coffee at the Edge of the Universe
In the first iteration, we will deal with a traditional RPC call; it takes one input argument and returns one output value.
In the first iteration, we will deal with a traditional RPC call; it takes one input argument and returns one output value.
In this iteration of the server, we add incoming or outgoing streams of requests or replies. We are not yet ready to take on the bi-directional stream.
In this iteration of the client, we add incoming or outgoing streams of requests or replies. We are not yet ready to take on the bi-directional stream.
Here we implement all four operations, including the bidirectional stream rpc method RouteChat(). We also add more abstractions to minimize the code required for each request.
Here we implement all four operations, including the bidirectional stream rpc method RouteChat(). We re-use the abstractions we created in the previous article.
Here we will look into how to use the newer - and much nicer - callback interface.
Here we implement all four operations using the newer - and much nicer - callback interface.
Here we implement all four operations as actual - usable - methods with event-callbacks.
Here we implement a client using QT 6.8 with an interactive QML UI!
A dive into asynchronous servers and clients using C++ and gRPC in 2023 - 2024
Latest articles
Lots of playing around with gRPC, some fixes in stbl. It's summer ;)