Core Readme: reorder Key Concepts, remove Distributed Tracing (#2532)

Co-authored-by: Anton Kolesnyk <antkmsft@users.noreply.github.com>
This commit is contained in:
Anton Kolesnyk 2021-07-01 11:00:19 -07:00 committed by GitHub
parent 6e73c1a623
commit d4e347b4f1
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -29,13 +29,13 @@ target_link_libraries(<your project name> 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<T>`.
- Polling long-running operations (LROs), via `Operation<T>`.
- 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