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'm building a service where each user can open a long-running task (think of a web scrapper), the users can insert many jobs into the queue, but generally do this in batches, how I can keep a processor "hot" for the user, so when he send subsequent jobs it is already open, and close it after a delay in the jobs sending
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
-
I'm building a service where each user can open a long-running task (think of a web scrapper), the users can insert many jobs into the queue, but generally do this in batches, how I can keep a processor "hot" for the user, so when he send subsequent jobs it is already open, and close it after a delay in the jobs sending
Beta Was this translation helpful? Give feedback.
All reactions