Hi, Had 2 questions regarding using "grpc.max_metadata_size"
1. It was not clear to me that `max_metadata_size` takes into account size of "detail" part of response. Can we allow setting "max_metadata_size" to -1 to represent unlimited as with `max_send_message_length` and `max_receive_message_length`? The exception that gets raised (at least from python) when you try and return with details larger then `max_metadata_size` is `(StatusCode.RESOURCE_EXHAUSTED, to-be-sent trailing metadata size exceeds peer limit` which imo is somewhat confusing as I didn't consider "details" to be trailing metadata, and it does not show up under the response call trailing metadata. 2. Is the equivalent of "max_metadata_size" exposed anywhere in grpc-go? As far as I can tell Java does expose it through netty params `maxHeaderListSize`. Thanks, Ashwin -- 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 grpc-io+unsubscr...@googlegroups.com. To post to this group, send email to grpc-io@googlegroups.com. 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/31385f13-7406-4af5-b124-f511098074f3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
