Hello Mark,
Thank you for your response, I'll take a look at the in-process transport.
I didn't think about avoiding (de-)serializing the protobufs, but now
that you mention it it would make a lot of sense.
Regards,
Pablo
On Wed, Aug 16, 2023 at 8:19 PM Mark D. Roth wrote:
>
> The closest
The closest thing we currently have to this is the in-process transport,
which uses the normal gRPC API but speaks to another process on the same
machine instead of using the networking stack. This still uses IPC, but it
avoids all of the overhead of TCP, HTTP/2, and gRPC framing on the wire.
Hello,
Imagine you are tasked with writing a C++ library to be used both as a DLL
for an application your company ships and also as the core of a backend
cloud service.
The library API relies on many structs and the overhead of using
protobuffers is deemed justifiable to obtain easily
