From d4e347b4f1657c89ea81501dcdf6ee1c0b2962e9 Mon Sep 17 00:00:00 2001 From: Anton Kolesnyk <41349689+antkmsft@users.noreply.github.com> Date: Thu, 1 Jul 2021 11:00:19 -0700 Subject: [PATCH] Core Readme: reorder Key Concepts, remove Distributed Tracing (#2532) Co-authored-by: Anton Kolesnyk --- sdk/core/azure-core/README.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/sdk/core/azure-core/README.md b/sdk/core/azure-core/README.md index 600678e39..06bc3c51a 100644 --- a/sdk/core/azure-core/README.md +++ b/sdk/core/azure-core/README.md @@ -29,13 +29,13 @@ target_link_libraries( PRIVATE Azure::azure-core) The main shared concepts of `Azure::Core` include: -- HTTP pipeline and HTTP policies such as retry and logging, which are configurable via service client specific options. - Handling streaming data and input/output (I/O) via `BodyStream` along with its derived types. - Accessing HTTP response details for the returned model of any SDK client operation, via `Response`. - Polling long-running operations (LROs), via `Operation`. - Exceptions for reporting errors from service requests in a consistent fashion via the base exception type `RequestFailedException`. - Abstractions for Azure SDK credentials (`TokenCredential`). - Replaceable HTTP transport layer to send requests and receive responses over the network. +- HTTP pipeline and HTTP policies such as retry and logging, which are configurable via service client specific options. ### Long Running Operations @@ -75,7 +75,6 @@ Three main ways of troubleshooting failures are: - Inspecting exceptions - Enabling logging (see [SDK Log Messages](#sdk-log-messages)) -- Distributed tracing (`Available in future release`) ### SDK Log Messages