flywithu/CryptoExchange.Net
1
0
Fork 0
mirror of https://github.com/JKorf/CryptoExchange.Net synced 2025-06-07 16:06:15 +00:00
Code Issues Releases Wiki Activity

Docs

Browse Source
This commit is contained in:
JKorf 2024-04-17 13:57:00 +02:00
parent 6f915a3739
commit 5b11d94f73
2 changed files with 11 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
README.md
View File

@ -43,7 +43,16 @@ Alternatively, sponsor me on Github using [Github Sponsors](https://github.com/s
## Release notes ## Release notes
* Version 7.3.0 - 17 Apr 2024 * Version 7.3.0 - 17 Apr 2024
* Rate limit update * Added new method for sending Rest requests which splits the static and dynamic parameters
* Refactored rate limiting implementation
* Ratelimiters now statically applied for all clients
* Added support for different rate limit window types
* Added modular configuration of rate limits
* Added rate limit check when creating websocket connections
* Added automatic handling and retry for Retry-After responses
* Added configuration for setting ratelimit for each individual endpoint
* Added event for when rate limit is triggered
* Added SocketClient GetSocketApiClientStates method
* Version 7.2.1 - 05 Apr 2024 * Version 7.2.1 - 05 Apr 2024
* Improved websocket reconnect logic * Improved websocket reconnect logic

2
docs/index.html
View File

@ -2276,7 +2276,7 @@ var binanceClient = new BinanceRestClient(new HttpClient(), logFactory, options
</p> </p>
<p> <p>
Client side rate limiting can only correctly work if there is only a single program talking to the exchange. When multiple different application send requests at the same time it's impossible for the client side to keep track of the rate limits. When using multiple concurrent applications it is advised to turn off rate limiting. Client side rate limiting can only correctly work if there is only a single program talking to the exchange. When multiple different application send requests at the same time it's impossible for the client side to keep track of the rate limits. When using multiple concurrent applications it is advised to turn off rate limiting. Also note that when requests are rate limited with RateLimitBehaviour.Wait that the order of the requests being send is not guarenteed.
</p> </p>
<p>Client side rate limiting is currently implemented for the following libraries:</p> <p>Client side rate limiting is currently implemented for the following libraries:</p>