Save and Load RateLimits to disk about chorus HOT 6 CLOSED

Implementing Serialize/Deserialize for Limit/LimitType (and RateLimits?) should be enough. Users can already read/write an instance's rate limits directly, which provides the most flexibility. Chorus doesn't need to care whether the user wants to store it as json or ron or xml in a file per instance or for multiple instances in a single file or where that file is or if it's actually in a database instead etc.

from chorus.

Fair point! Another case of the simplest solution being the best haha

from chorus.

i dont think storing ratelimits on disk would be a good idea?

from chorus.

Elaborate? Storing the ratelimits is important if you want to accurately keep track of what your current rate limits are. If you restart the library/application and you do not have them saved anywhere, then it'll just reset to the normal, unchanged ratelimits, and you'd run into limits

from chorus.

which is fine, how are you gonna handle different ratelimit implementations?
or well, as in spacebar-server-ts, the "global" rate limits?

from chorus.

If you are referring to the GlobalRegister and GlobalMessage limits: We don't track those. We cannot even track those, AFAIK.

from chorus.