Articles with tag gRPC

Fun with gRPC and C++

Published:

A dive into asynchronous servers and clients using C++ and gRPC in 2023

Read on...

Exploring how to implement the server using gRPC async callbacks

Published:

Here we implement all four operations using the newer - and much nicer - callback interface.

Read on...

Exploring how to implement the client using gRPC async callbacks

Published:

Here we implement all four operations as actual - usable - methods with event-callbacks.

Read on...

Exploring the async callback interface for gRPC in C++

Published:

Here we will look into how to use the newer - and much nicer - callback interface.

Read on...

Monthly update, July 2023

Published:

Lots of playing around with gRPC, some fixes in stbl. It's summer ;)

Read on...

Implementing a unary, async client

Published:

In the first iteration, we will deal with a traditional RPC call; it takes one input argument and returns one output value.

Read on...

Implementing an async client with one message and one stream.

Published:

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.

Read on...

Implementing the full routeguide async server

Published:

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.

Read on...

Implementing the full routeguide async client

Published:

Here we implement all four operations, including the bidirectional stream rpc method RouteChat(). We re-use the abstractions we created in the previous article.

Read on...

Implementing a unary, async server

Published:

In the first iteration, we will deal with a traditional RPC call; it takes one input argument and returns one output value.

Read on...

Implementing an async server with one message and one stream.

Published:

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.

Read on...