You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of right now, neocord only has support for memory caching... I'd like to add ways to use different methods like redis, mongodb, or any other database. But I have no idea how to do so.
So here we have imported the Client and DiscordStructure.
The DiscordStructure enum is used to identify structures that can be cached within neocord like a Message, Role, etc...
We have also imported the Redis Data Engine and the Sweepers object.
The sweepers object contains pre-made sweepers for some of the structures.
In this case the redis data engine caches messages/presences and everything else will be stored within memory. I've also declared the sweepers option, only enabling a message sweeper which gets ran every 5 minutes and checks whether the message is older than 30 minutes and if it is it will be removed from the redis cache.
This is all just a very cool concept that might come to life but until there are more contributors this wont happen for quite a while.
The text was updated successfully, but these errors were encountered:
The internals of the caching is what I would really like help on, I have no ideas on how this would work internally... especially with all of the different managers and stuff.
As of right now, neocord only has support for memory caching... I'd like to add ways to use different methods like redis, mongodb, or any other database. But I have no idea how to do so.
Setup?
This is how I would like it to look
(typescript)
:So here we have imported the Client and DiscordStructure.
We have also imported the Redis Data Engine and the Sweepers object.
In this case the redis data engine caches messages/presences and everything else will be stored within memory. I've also declared the sweepers option, only enabling a message sweeper which gets ran every 5 minutes and checks whether the message is older than 30 minutes and if it is it will be removed from the redis cache.
This is all just a very cool concept that might come to life but until there are more contributors this wont happen for quite a while.
The text was updated successfully, but these errors were encountered: