Timeline for How to Handle Concurrent Refresh Token Requests
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 20 at 13:22 | comment | added | Bad Boy | I also had to add a cleanup job to remove that refresh token from slices, you can not store them forever. it will just keep expanding. | |
| Nov 20 at 13:20 | comment | added | Bad Boy | Thanks for this complete answer, and yes this appproach is the one that i actually implemented yesterday, I could not find anything better. So i have one slice for storing tokens with Locks, and then another map for storing the result for that token with Locks. The only thing that i was not sure about was that if i should use redis and its locking mechanism to handle this for me or should i implement the locking system all by myself...??? | |
| Nov 20 at 11:54 | history | answered | gnasher729 | CC BY-SA 4.0 |