Skip to content

Commit 75cb02a

Browse files
authored
Group gRPC client topics under a TOC parent (#19886)
1 parent 5e87d7d commit 75cb02a

2 files changed

Lines changed: 12 additions & 10 deletions

File tree

aspnetcore/grpc/client.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ A .NET gRPC client library is available in the [Grpc.Net.Client](https://www.nug
1717

1818
## Configure gRPC client
1919

20-
gRPC clients are concrete client types that are [generated from *\*.proto* files](xref:grpc/basics#generated-c-assets). The concrete gRPC client has methods that translate to the gRPC service in the *\*.proto* file.
20+
gRPC clients are concrete client types that are [generated from *\*.proto* files](xref:grpc/basics#generated-c-assets). The concrete gRPC client has methods that translate to the gRPC service in the *\*.proto* file. For example, a service called `Greeter` generates a `GreeterClient` type with methods to call the service.
2121

2222
A gRPC client is created from a channel. Start by using `GrpcChannel.ForAddress` to create a channel, and then use the channel to create a gRPC client:
2323

@@ -41,7 +41,7 @@ var counterClient = new Count.CounterClient(channel);
4141

4242
A gRPC client must use the same connection-level security as the called service. gRPC client Transport Layer Security (TLS) is configured when the gRPC channel is created. A gRPC client throws an error when it calls a service and the connection-level security of the channel and service don't match.
4343

44-
To configure a gRPC channel to use TLS, ensure the server address starts with `https`. For example, `GrpcChannel.ForAddress("https://localhost:5001")` uses HTTPS protocol. The gRPC channel automatically negotates a connection secured by TLS and uses a secure connection to make gRPC calls.
44+
To configure a gRPC channel to use TLS, ensure the server address starts with `https`. For example, `GrpcChannel.ForAddress("https://localhost:5001")` uses HTTPS protocol. The gRPC channel automatically negotiates a connection secured by TLS and uses a secure connection to make gRPC calls.
4545

4646
> [!TIP]
4747
> gRPC supports client certificate authentication over TLS. For information on configuring client certificates with a gRPC channel, see <xref:grpc/authn-and-authz#client-certificate-authentication>.

aspnetcore/toc.yml

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -714,16 +714,20 @@
714714
uid: grpc/services
715715
- name: Create Protobuf messages
716716
uid: grpc/protobuf
717+
- name: Versioning gRPC services
718+
uid: grpc/versioning
719+
- name: Call gRPC services with C#
720+
items:
721+
- name: Overview
722+
uid: grpc/client
723+
- name: gRPC client factory integration
724+
uid: grpc/clientfactory
725+
- name: Deadlines and cancellation
726+
uid: grpc/deadlines-cancellation
717727
- name: gRPC services with ASP.NET Core
718728
uid: grpc/aspnetcore
719-
- name: Call gRPC services with .NET client
720-
uid: grpc/client
721-
- name: gRPC client factory integration
722-
uid: grpc/clientfactory
723729
- name: Use gRPC in browser apps
724730
uid: grpc/browser
725-
- name: Deadlines and cancellation
726-
uid: grpc/deadlines-cancellation
727731
- name: Configuration
728732
uid: grpc/configuration
729733
- name: Authentication and authorization
@@ -734,8 +738,6 @@
734738
uid: grpc/security
735739
- name: Performance best practices
736740
uid: grpc/performance
737-
- name: Versioning gRPC services
738-
uid: grpc/versioning
739741
- name: Manage Protobuf references with dotnet-grpc
740742
uid: grpc/dotnet-grpc
741743
- name: Test services with gRPC tools

0 commit comments

Comments
 (0)