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
Calling Panoptes.connect for each request will replace the internal client instance and run through oauth setup and token generation for each request.
Normal practice in multithreaded env would be to setup a connection pooler at boot that requests use to checkout a client instance for use. A forking server could use a single shared instance as long as the client instance is setup after the fork.
It seems flask allows the use of request contexts but that requires connecting and discarding the client on each request, no better than what currently exists frankly.
The text was updated successfully, but these errors were encountered:
aggregation-for-caesar/panoptes_aggregation/panoptes/userify.py
Line 165 in b6b7ee4
Calling
Panoptes.connect
for each request will replace the internal client instance and run through oauth setup and token generation for each request.Normal practice in multithreaded env would be to setup a connection pooler at boot that requests use to checkout a client instance for use. A forking server could use a single shared instance as long as the client instance is setup after the fork.
It seems flask allows the use of request contexts but that requires connecting and discarding the client on each request, no better than what currently exists frankly.
The text was updated successfully, but these errors were encountered: