I have a streaming service that sends the same message to multiple connected 
clients. 
I'm wondering if grpc (or protobuf itself) is smart enough to cache the 
serialised form of a message, so that the serialisation cost is not incurred 
once per connected client?
Otherwise, what is the cleanest strategy for optimising this?
Thanks, Mark

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/2b4a9b04-8379-4867-9ed4-761908e690c8%40googlegroups.com.

Reply via email to