Edsko de Vries
Edsko de Vries
References: * https://grpc.io/docs/guides/metadata/ (background) * https://github.com/grpc/proposal/blob/7c05212d14f4abef5f74f71695f95ba8dd3f7dd3/G1-true-binary-metadata.md (spec) The C++ reference implementation in the gRPC interop tests enables this in the initial HTTP2 `SETTINGS` frame (Wireshark shows this as `Unknown (65027)...
See * https://grpc.io/docs/guides/custom-backend-metrics/ * https://github.com/grpc/proposal/blob/master/A51-custom-backend-metrics.md Note that this is currently only supported by C++, Java and Go (not supported by ASP, Dart, Node, JavaScript, PHP, Objective C, Ruby, Python).
`Compression` is currently defined as ```haskell data Compression = Compression { compressionId :: CompressionId , compress :: Lazy.ByteString -> Lazy.ByteString , decompress :: Lazy.ByteString -> Lazy.ByteString } ``` The type...
References: * https://grpc.io/docs/guides/auth/ * https://grpc.io/docs/languages/python/alts/ . This is not part of the gRPC spec proper but all example servers support it. Not entirely sure how important this is.
I _think_ that this is a limitation of `http2`, but I do not know for sure. One potential clue I found during debugging this is that perhaps things go wrong...
The spec says: > Implementations should expect broken deployments to send non-200 HTTP > status codes in responses as well as a variety of non-GRPC content-types > and to omit...
This requires a bit of work in setting up a good weeder config.
See https://github.com/grpc/grpc/blob/master/doc/server-reflection.md , https://www.youtube.com/watch?v=dDr-8kbMnaw .
If nothing else, this would make it possible to verify that compression is being used when enabled, without requiring Wireshark.
`Boxed` vectors are already supported, but adding support for the other flavours is a bit trickier: * `Storable` and `Primitive` vectors have a `Storable` constraint on the element type, and...