mirror of
https://github.com/invoke-ai/InvokeAI
synced 2024-08-30 20:32:17 +00:00
b777dba430
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. |
||
|---|---|---|
| .. | ||
| config | ||
| models | ||
| __init__.py | ||
| batch_manager_storage.py | ||
| batch_manager.py | ||
| board_image_record_storage.py | ||
| board_images.py | ||
| board_record_storage.py | ||
| boards.py | ||
| default_graphs.py | ||
| events.py | ||
| graph.py | ||
| image_file_storage.py | ||
| image_record_storage.py | ||
| images.py | ||
| invocation_queue.py | ||
| invocation_services.py | ||
| invocation_stats.py | ||
| invoker.py | ||
| item_storage.py | ||
| latent_storage.py | ||
| model_manager_service.py | ||
| processor.py | ||
| resource_name.py | ||
| sqlite.py | ||
| urls.py | ||