Hi gRPC Users,

*TL;DR*: New API for per-method, generic method handling on the C++ server
side.

*Overview*: Previously, a gRPC C++ server would either be generic, or use
proto specific generated code. Mixing the two was possible, but needed a
lot of hacking. Now, there is an option to mark a single method as *Raw*.
This signifies to the generated code that the server should handle the
method in terms of ByteBuffer, not in terms of the protobuf objects. This
can be useful to special case the serialization for critical methods.

More details can be found in these two gRFCs:

   - Exposing GrpcProtoBuffer{Reader|Writer}:
   L25-expose-buffer-reader-writer.md
   
<https://github.com/grpc/proposal/blob/master/L25-expose-buffer-reader-writer.md>
   - C++ Raw API: L26-cpp-raw-codegen-api.md
   <https://github.com/grpc/proposal/blob/master/L26-cpp-raw-codegen-api.md>


The implementation (along with example usage in the tests) can be found in:

   - Exposing GrpcProtoBuffer{Reader|Writer}: #14541
   <https://github.com/grpc/grpc/pull/14541>
   - C++ Raw API: #15771 <https://github.com/grpc/grpc/pull/15771>

-- 
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/CAPYwnkgY%3D7MjF1AsrrCXc66mW-O3qOGejG8M4inREaqOXKX__A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to