diff options
| author |  Jan Tattermusch <jtattermusch@users.noreply.github.com> | 2017-02-22 15:18:34 +0100 |
|---|---|---|
| committer |  GitHub <noreply@github.com> | 2017-02-22 15:18:34 +0100 |
| commit | 012fc00ada6504b75fff5da2cc5bde53344236ab (patch) | |
| tree | a76a1535936d4b62737a6cafe26ed09be5bf4e3f /doc/internationalization.md | |
| parent | ec5e730d47561d14045747031f824216a694f3dc (diff) | |
Address comments.
Diffstat (limited to 'doc/internationalization.md')
| -rw-r--r-- | doc/internationalization.md | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/doc/internationalization.md b/doc/internationalization.md index a39a5eef89..b82785207b 100644 --- a/doc/internationalization.md +++ b/doc/internationalization.md @@ -10,8 +10,9 @@ While some API elements need to be able to represent non-english content, some a for simplicity & performance reasons. ### Method name (in RPC Invocation) -Method names are ASCII-only. Most gRPC services will use protobuf which only allows ASCII based method names anyway. -Also, handling method names is a very hot code path. +Method names are ASCII-only and may only contain characters allowed by HTTP/2 text header values. That should not +be very limiting as most gRPC services will use protobuf which only allows method names from an even more restricted ASCII subset. +Also, handling method names is a very hot code path so any additional encoding/decoding step is to be avoided. Recommended representation in language-specific APIs: string type. @@ -39,6 +40,6 @@ Allowed values are defined by HTTP/2 standard (metadata values are represented a Recommended representation in language-specific APIs: string. -### Channel name +### Channel target (in channel creation) TBD |