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
Hi, thanks for the package!
I have an app that works the following way: people trust me with their api keys and secrets, I add them to my app, the app makes api calls using their api credentials. Since the app makes calls on behalf of multiple different users, the shared config object becomes an issue. I have to be extra careful to not have simultaneous api calls with different user configs, because I'm afraid when calling init for request B while request A hasn't been sent yet, request A will use request B config. Can you please confirm that this sort of error is in fact possible during simultaneous requests ? If yes, is it possible to initiate multiple instances, each with their own config ?
The text was updated successfully, but these errors were encountered:
Hi, thanks for the package!
I have an app that works the following way: people trust me with their api keys and secrets, I add them to my app, the app makes api calls using their api credentials. Since the app makes calls on behalf of multiple different users, the shared config object becomes an issue. I have to be extra careful to not have simultaneous api calls with different user configs, because I'm afraid when calling init for request B while request A hasn't been sent yet, request A will use request B config. Can you please confirm that this sort of error is in fact possible during simultaneous requests ? If yes, is it possible to initiate multiple instances, each with their own config ?
The text was updated successfully, but these errors were encountered: