InvokeAI/invokeai/app/api
psychedelicious b777dba430 feat: batch events
When a batch creates a session, we need to alert the client of this. Because the sessions are created by the batch manager (not directly in response to a client action), we need to emit an event with the session id.

To accomodate this, a secondary set of sio sub/unsub/event handlers are created. These are specifically for batch events. The room is the `batch_id`.

When creating a batch, the client subscribes to this batch room.

When the batch manager creates a batch session, a `batch_session_created` event is emitted in the appropriate room.  It includes the session id. The client then may subscribe to the session room, and all socket stuff proceeds as it did before.
2023-09-05 21:17:33 +10:00
..
routers fix(api): fix duplicate operation id 2023-09-05 16:06:35 +10:00
dependencies.py Merge branch 'main' into feat/batch-graphs 2023-08-18 15:40:34 -04:00
events.py Event service will now sleep for 100ms between polls instead of 1ms, reducing CPU usage significantly 2023-04-23 21:27:02 +01:00
sockets.py feat: batch events 2023-09-05 21:17:33 +10:00