A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/App-vNext/Polly/issues/426 below:

Better name ExecutionKey and ExecutionGuid · Issue #426 · App-vNext/Polly · GitHub

The execution context keys ExecutionKey and ExecutionGuid have caused confusion with similar names.

Polly v6.0 presents an opportunity to clarify the names prior to their wider use in events and metrics.

v5.x name Proposed v6.0 name Rationale Notes ExecutionKey OperationKey Policies are usable at multiple call sites. The OperationKey is a user-definable string key intended to allow tagging the operation the policy is being used for (eg "GetCustomerDetails", "[GET] github/users/x"), for distinguishing different usages in logging and metrics. A read-only property Context.ExecutionKey => OperationKey (with suitable intellisense) could be left on Context, in recognition of the fact that the term 'execution key' does exist in some external documentation.
An alternative name could be UsageKey. ExecutionGuid CorrelationId CorrelationId is a more typical name for a unique id correlating all events linked to a particular request or operation. The property has as yet formed no part of the Polly API beyond being exposed (it was added in preparation for metrics).

Polly v5.9.0 would pre-advertise the deprecations per semver, with [ObsoleteAttribute()], prior to breaking changes (removing deprecated versions) in Polly v6.0.


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4