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
I know it sounds stupid and it really propably is, but, given that for every user that has his own key u:a:<userid>. The type could be a hashtable that is indexed in with the api key (the user id is known to user an posseses no security risk in disclosing), but that would mean i would literally have to store something just for the return value not not be nil and the auth to pass, for now i have nothing to cache as all operations eventually write to db and so there is no use in caching any of the permissions.
Would it be a bad idea to use a bloom filter that contains all the viable api keys for such user instead of hashtable?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I know it sounds stupid and it really propably is, but, given that for every user that has his own key
u:a:<userid>. The type could be a hashtable that is indexed in with the api key (the user id is known to user an posseses no security risk in disclosing), but that would mean i would literally have to store something just for the return value not not be nil and the auth to pass, for now i have nothing to cache as all operations eventually write to db and so there is no use in caching any of the permissions.Would it be a bad idea to use a bloom filter that contains all the viable api keys for such user instead of hashtable?
All reactions