This repository has been archived by the owner on Nov 16, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 85
moved setting the base url and the management key header to a common place for all consumers #20
Open
smstuebe
wants to merge
1
commit into
microsoft:master
Choose a base branch
from
smstuebe:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we possibly reuse the HTTP Client if we've already created one? Currently we'd be creating a new client for each request.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you can. I thought about it, but didn't want to introduce side effects regarding DNS cache stuff. If you wan't just add
Lazy<HttpClient>
:)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe we we're originally new-ing up an instance of HttpClient for every request so your change isn't breaking the existing solution but rather brought to my attention to something we could improve.
I'm guessing the DNS caching side effect you mention is related to the HttpClient instance holding DNS info for 2 minutes? If thats the case then we should* be safe given we use API Management in production and the DNS is locked down and not changing but with that said, I think we can make this all work nicely...
One vs multiple clients
To quote the docs on HttpClient:
Sockets can be held for up to 4 minutes per request so this might actually be causing our network stability issues when we send too many requests. I'd love @robinmanuelthiel to share his thoughts on this as well.
Possible solution to DNS Cache with 1 instance
We could use set the
DnsRefreshTimeout
property of ServicePointManager class to set our own DNS refresh timeout to something more sensible (if we REALLY needed to). This could help mitigate any issues with DNS caching.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't get me wrong. I'm pro caching, too. I just did not want to change the current behavior :P