ClientModel: Evaluate consistency across transports with regard to casing of request.Method

[annelo-msft]

System.ClientModel APIView

• PipelineProcessor/IEnumerable - ClientModel: Rework PipelineProcessor #40691
• KeyCredential/Policy - ClientModel: KeyCredentialAuthenticationPolicy API updates #40705
• RequestOptions.Apply investigation and rework - ClientModel: Remove RequestOptions.Apply #40706
• Evaluate whether there is consistency across transports with regard to handling casing of request.Method
• Evaluate whether having both AddHeader and SetHeader methods on RequestOptions overly complicates the public APIs - if it does not, add SetHeader and track the work needed for generated CreateRequest routines to support it.
• Evaluate how hard it is to remove IEnumerable from MessageHeaders
• Can we make ResponseStatusClassifier internal? - ClientModel: Make ResponseStatusClassifier internal #40709
• Make Azure.Core ClientOptions inherit from ClientModel PipelineOptions
• Decide whether RequestOptions and BinaryContent should move into .Primitives namespace given their use in protocol methods and not convenience methods
  • Investigation: Understand whether Storage convenience methods would reasonably use these types
• Update KeyCredentialAuthenticationPolicy per:
  • KrzysztofCwalina 1 hour ago
    header name should be optional. The default value should be "Authorization"
  • KrzysztofCwalina [1 hour ago]
    I would also love to have a ctor for the most common scenario. We should also consider this ctor to take string in addition to KeyCredentail. For context, this is to enable RestClient scenarios.
• Update PipelinePolicy per:
  • KrzysztofCwalina 1 hour ago
    I would like policies to have the following property:
    public PipelinePosition DefaultPosition { get; }
    In addition, all APIs that take a policy and the position (e.g. Add(PipelInePolisy, PipelinePosition) should default the second parameter. This would allow adding policies without having to specify the position (which users often don't know what it should be),This is to support RestClient scenarios.