From ba955c44b935d8c0a76bc57451d7f006994f804a Mon Sep 17 00:00:00 2001 From: Tom Dykstra Date: Mon, 25 Jan 2021 13:44:51 -0800 Subject: [PATCH 1/3] ServicePoint not used in .NET Core --- docs/framework/network-programming/managing-connections.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/framework/network-programming/managing-connections.md b/docs/framework/network-programming/managing-connections.md index 00a2d363114d6..d89a84ed67762 100644 --- a/docs/framework/network-programming/managing-connections.md +++ b/docs/framework/network-programming/managing-connections.md @@ -1,7 +1,7 @@ --- title: "Managing Connections" description: Learn how applications that use HTTP for data resources can use the .NET Framework ServicePoint and ServicePointManager classes to manage connections. -ms.date: "03/30/2017" +ms.date: 01/25/2021 dev_langs: - "csharp" - "vb" @@ -22,6 +22,9 @@ ms.assetid: 9b3d3de7-189f-4f7d-81ae-9c29c441aaaa # Managing Connections Applications that use HTTP to connect to data resources can use the .NET Framework's and classes to manage connections to the Internet and to help them achieve optimum scale and performance. + +> [!NOTE] +> `ServicePoint` and `ServicePointManager` are considered legacy and are only stubbed out in .NET Core, .NET 5, and later versions. Very little is used by any of the networking stack. They are referenced from `HttpWebRequest` (also legacy) in only a few places, in an attempt to respect some globally-set settings. `ServicePoint` doesn't track anything about current connections used by `HttpClient` (or `HttpWebRequest`, which layers on top of it) and is hardcoded to return 0 for . The **ServicePoint** class provides an application with an endpoint to which the application can connect to access Internet resources. Each **ServicePoint** contains information that helps optimize connections with an Internet server by sharing optimization information between connections to improve performance. From 836f6b37d61ec069360e2d3e9bd183d515dbfd77 Mon Sep 17 00:00:00 2001 From: Tom Dykstra Date: Fri, 29 Jan 2021 15:29:09 -0800 Subject: [PATCH 2/3] Update docs/framework/network-programming/managing-connections.md Co-authored-by: Genevieve Warren <24882762+gewarren@users.noreply.github.com> --- docs/framework/network-programming/managing-connections.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/framework/network-programming/managing-connections.md b/docs/framework/network-programming/managing-connections.md index d89a84ed67762..3601c0ab06fda 100644 --- a/docs/framework/network-programming/managing-connections.md +++ b/docs/framework/network-programming/managing-connections.md @@ -24,7 +24,7 @@ ms.assetid: 9b3d3de7-189f-4f7d-81ae-9c29c441aaaa Applications that use HTTP to connect to data resources can use the .NET Framework's and classes to manage connections to the Internet and to help them achieve optimum scale and performance. > [!NOTE] -> `ServicePoint` and `ServicePointManager` are considered legacy and are only stubbed out in .NET Core, .NET 5, and later versions. Very little is used by any of the networking stack. They are referenced from `HttpWebRequest` (also legacy) in only a few places, in an attempt to respect some globally-set settings. `ServicePoint` doesn't track anything about current connections used by `HttpClient` (or `HttpWebRequest`, which layers on top of it) and is hardcoded to return 0 for . +> `ServicePoint` and `ServicePointManager` are considered legacy and and exist only as stubs in .NET Core, .NET 5, and later versions. Very little is used by any of the networking stack. They are referenced from `HttpWebRequest` (also legacy) in only a few places, in an attempt to respect some global settings. `ServicePoint` doesn't track anything about current connections used by `HttpClient` (or `HttpWebRequest`, which layers on top of it) and is hardcoded to return 0 for . The **ServicePoint** class provides an application with an endpoint to which the application can connect to access Internet resources. Each **ServicePoint** contains information that helps optimize connections with an Internet server by sharing optimization information between connections to improve performance. From 32121d61b9730d7f44b018d32ba5e70400d47d94 Mon Sep 17 00:00:00 2001 From: Tom Dykstra Date: Mon, 1 Feb 2021 08:13:18 -0800 Subject: [PATCH 3/3] Update docs/framework/network-programming/managing-connections.md Co-authored-by: Karel Zikmund --- docs/framework/network-programming/managing-connections.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/framework/network-programming/managing-connections.md b/docs/framework/network-programming/managing-connections.md index 3601c0ab06fda..26a275e7195ee 100644 --- a/docs/framework/network-programming/managing-connections.md +++ b/docs/framework/network-programming/managing-connections.md @@ -24,7 +24,7 @@ ms.assetid: 9b3d3de7-189f-4f7d-81ae-9c29c441aaaa Applications that use HTTP to connect to data resources can use the .NET Framework's and classes to manage connections to the Internet and to help them achieve optimum scale and performance. > [!NOTE] -> `ServicePoint` and `ServicePointManager` are considered legacy and and exist only as stubs in .NET Core, .NET 5, and later versions. Very little is used by any of the networking stack. They are referenced from `HttpWebRequest` (also legacy) in only a few places, in an attempt to respect some global settings. `ServicePoint` doesn't track anything about current connections used by `HttpClient` (or `HttpWebRequest`, which layers on top of it) and is hardcoded to return 0 for . +> `ServicePoint` and `ServicePointManager` are considered legacy on .NET Core, .NET 5, and later versions. Most of their properties and methods are not implemented in these versions. When they are implemented, they don't affect or track anything about `HttpClient` networking APIs. The **ServicePoint** class provides an application with an endpoint to which the application can connect to access Internet resources. Each **ServicePoint** contains information that helps optimize connections with an Internet server by sharing optimization information between connections to improve performance.