Skip to content

Consider moving NetworkTimeout to HttpPipelineTransportOptions #37736

@JoshLove-msft

Description

@JoshLove-msft
          > Again to ground my understanding - if a caller sets a RetryPolicy, does that mean we completely ignore RetryOptions? (It sounds like what you're saying above, but I want to confirm I'm understanding correctly.)

Nope, we still will thread the NetworkTimeout through to the ResponseBodyPolicy. I agree that the story is a bit confusing with how we are presenting RetryPolicy as an override to RetryOptions. I would suggest we consider moving NetworkTimeout somewhere that is more sensible (perhaps TransportOptions) as @christothes suggests.

Originally posted by @JoshLove-msft in #37715 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Azure.CoreClientThis issue is related to a non-management package

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions