Lines Matching +full:metadata +full:- +full:specific

5 This document describes gRPC API and behavior specifics when used in a non-english environment.
9 …ome API elements need to be able to represent non-english content, some are intentionally left as …
13 Method names are ASCII-only and may only contain characters allowed by HTTP/2 text header values. T…
17 Recommended representation in language-specific APIs: string type.
20 Host names are punycode encoded, but the user is responsible for providing the punycode-encoded str…
22 Recommended representation in language-specific APIs: string/unicode string.
24 NOTE: overriding host name when invoking RPCs is only supported by C-core based gRPC implementation…
28 Status messages are expected to contain national-alphabet characters.
29 Allowed values are unicode strings (content will be percent-encoded on the wire).
31 Recommended representation in language-specific APIs: unicode string.
33 ### Metadata key
34 Allowed values are defined by HTTP/2 standard (metadata keys are represented as HTTP/2 header/trail…
36 Recommended representation in language-specific APIs: string.
38 ### Metadata value (text-valued metadata)
39 Allowed values are defined by HTTP/2 standard (metadata values are represented as HTTP/2 header/tra…
41 Recommended representation in language-specific APIs: string.