Dear Craig,
thanks for the very quick reply! I found it relatively easy to
serialize messages with protobuf's SerializeToString() method. But
how would I send this with grpc? Are there examples of the generic
APIs, or can you point me to whatever corresponds to a "send"
function?
All the best,
Mario
On 18.03.2017 16:47, Craig Tiller wrote:
> Look to the generic APIs: they're async and perform no serialization.
>
>
> On Sat, Mar 18, 2017, 8:29 AM Mario Emmenlauer <[email protected]
> <mailto:[email protected]>> wrote:
>
>
> I'd like to implement client-side caching in a C++ client, by storing
> the request and reply in a map, and answering subsequent requests from
> the map it possible. If something like this exists, I'd be happy to know!
> If it does not exist, it seems straightforward enough to implement. The
> protobuf serialized forms of the messages seem quite ideal for this(?)
>
> My question: is there an example how to use grpc with protobuf, but
> perform the serialization "by hand" so it can be cached? Since I use
> asynchronous calls, it would also be great to know which response
> matches which request.
--
You received this message because you are subscribed to the Google Groups
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/grpc-io.
To view this discussion on the web visit
https://groups.google.com/d/msgid/grpc-io/3300ce8a-e38f-83ba-ee9e-62ee916a450f%40emmenlauer.de.
For more options, visit https://groups.google.com/d/optout.
