Tree:
b745a3cd6d
0.9
2.4.1
3.0-old
4.0
5.0
absalias
blank
ci/docs
dev
dispose-tweaks
experiment/doc-redesign
experiment/emoji-validation
feature/3.0-serialization-generator
feature/automod
feature/marshal-by-ref
feature/reset-fater
feature/rest-on-socket
fix/exception-on-logout
fix/fix-thread-member-download
fix/if-docs
next
release/1.0.2
release/2.4.0
v4/message-builder
v4/state-cache-providers
voice-allocs
1.0
1.0-rc
1.0.0-rc2
1.0.1
1.0.2
2.0
2.0.0
2.0.0-beta
2.0.1
2.1.0
2.1.1
2.2.0
2.3.0
2.3.1
2.4.0
3.0.0
3.1.0
3.2.0
3.2.1
3.3.0
3.3.1
3.3.2
3.4.0
3.4.1
3.5.0
3.6.0
3.6.1
3.7.0
3.7.1
3.7.2
3.8.0
3.8.1
3.9.0
docs-0.9
1 Commits (b745a3cd6d03a642a1b36da8340d6114c5086c60)
1 Commits (b745a3cd6d03a642a1b36da8340d6114c5086c60)
| Author | SHA1 | Message | Date |
|---|---|---|---|
 emorell96
|
b745a3cd6d |
Added two Extension methods "AddScopedDiscordRestClient" and "AddTransientDiscordRestClient" to allow for easier addition of scoped, and transient DiscordRestClients, it's left up to the user which one is more convenient to use for his/her application, and at the end of the day it doesn't risk running out of sockets since it uses IHttpClientFactory under the hood.
This means that it moves the useProxy boolean parameter here, not sure how much that affects the rest of the library. def an addition to consider. And something that more accustomed users/contributors will be able to answer. The main advantage of having such a method in the future could be adding resiliency. Major resiliency by for example using Polly in a simple way see: https://docs.microsoft.com/en-us/dotnet/architecture/microservices/implement-resilient-applications/implement-http-call-retries-exponential-backoff-polly for example. Of course this means that the user would have to use DI (which is anyways a good practice), but I left the other default ones so that it wouldn't bring any breaking changes. |
5 years ago |