Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
G
Grpc
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
tci-gateway-module
Grpc
Commits
4a4e22d1
Commit
4a4e22d1
authored
Jul 17, 2015
by
David G. Quintas
Browse files
Options
Downloads
Patches
Plain Diff
client config README small fixes
Tiny typo plus addition of URI RFC reference and formatting.
parent
f87a0984
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
src/core/client_config/README.md
+16
-14
16 additions, 14 deletions
src/core/client_config/README.md
with
16 additions
and
14 deletions
src/core/client_config/README.md
+
16
−
14
View file @
4a4e22d1
...
@@ -24,7 +24,7 @@ Load Balancing
...
@@ -24,7 +24,7 @@ Load Balancing
Load balancing configuration is provided by a grpc_lb_policy object, stored as
Load balancing configuration is provided by a grpc_lb_policy object, stored as
part of grpc_client_config.
part of grpc_client_config.
A load balancing polic
ies
primary job is to pick a target server given only the
A load balancing polic
y
primary job is to pick a target server given only the
initial metadata for a request. It does this by providing a grpc_subchannel
initial metadata for a request. It does this by providing a grpc_subchannel
object to the owning channel.
object to the owning channel.
...
@@ -39,15 +39,16 @@ decisions (for example, by avoiding disconnected backends).
...
@@ -39,15 +39,16 @@ decisions (for example, by avoiding disconnected backends).
Configured sub-channels are fully setup to participate in the grpc data plane.
Configured sub-channels are fully setup to participate in the grpc data plane.
Their behavior is specified by a set of grpc channel filters defined at their
Their behavior is specified by a set of grpc channel filters defined at their
construction. To customize this behavior, resolvers build
grpc_subchannel_factory
construction. To customize this behavior, resolvers build
objects, which use the decorator pattern to customize
construction arguments for
grpc_subchannel_factory
objects, which use the decorator pattern to customize
concrete grpc_subchannel instances.
construction arguments for
concrete grpc_subchannel instances.
Naming for GRPC
Naming for GRPC
===============
===============
Names in GRPC are represented by a URI.
Names in GRPC are represented by a URI (as defined in
[
RFC 3986
](
https://tools.ietf.org/html/rfc3986
)
).
The following schemes are currently supported:
The following schemes are currently supported:
...
@@ -56,5 +57,6 @@ dns:///host:port - dns schemes are currently supported so long as authority is
...
@@ -56,5 +57,6 @@ dns:///host:port - dns schemes are currently supported so long as authority is
release)
release)
unix:path - the unix scheme is used to create and connect to unix domain
unix:path - the unix scheme is used to create and connect to unix domain
sockets - the authority must be empty, and the path represents
sockets - the authority must be empty, and the path
the absolute or relative path to the desired socket
represents the absolute or relative path to the desired
socket
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
sign in
to comment