Re: [grpc-io] Rational behind mapping HTTP 429 to gRPC UNAVAILABLE

google/rpc/code.proto has the HTTP mappings. Those are REST-centric and are for converting *to* HTTP status code. Multiple of them are obviously wrong for gRPC (e.g., NOT_FOUND→404) and multiple of them are... weak... mapp

[grpc-io] Rational behind mapping HTTP 429 to gRPC UNAVAILABLE

Hi, According to http-grpc-status-mapping.md , HTTP 429 Too Many Requests is translated into gRPC UNAVAILABLE rather than RESOURCE_EXHAUSTED. However, at some point in the past, statuscodes.md

[grpc-io] io_uring support for gRPC's C++ implementation

Hi, Are there any plans to add io_uring support (or other alternatives to reduce the number/frequency of system calls) to gRPC, in particular the C++ implementation? If so, is there a timeline for this work to land? Otherwise, is the idea rejected for any specific reason? -- You received this

[grpc-io] gRFC P6: grpc-io-announce mailing list

Hi, Eric and I put together a gRFC to create an "announce" mailing list to have a high-signal method to notify users of important announcements, especially for security and reliability issues. https://github.com/grpc/proposal/pull/458 Feedback welcome. Best, Gina -- Jung-Yu (Gina) Yeh Softwa