Handle Audiobookshelf user_item_progress_updated realtime events #8
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
Device testing of GitHub PR #83 showed that BookWave's realtime socket authenticates and survives profile switching, but remote playback progress changes do not produce
Applying a realtime account update.Current Audiobookshelf playback-session code emits
user_item_progress_updatedwhen/api/session/.../syncor local-session sync changes progress. BookWave currently handlesuser_updatedbut not this more specific playback-progress event, so the event is silently ignored and progress is learned later through REST fallback instead.Observed device evidence:
written=1, proving there was newer server progress available.Scope
user_item_progress_updatedSocket.IO payload contract.Important boundary: realtime does not drive the live player
This issue is protocol coverage and low-latency progress ingestion only.
A Socket.IO progress event must not directly seek active playback. While BookWave is actively playing, its live player/journal/outbox remain authoritative for this device. While paused, the pushed position may become an input/candidate for the next resume decision, but Socket.IO cannot replace the REST fallback because events are not replayed after a disconnect/background/process death.
The shared resume policy and control-surface integration are tracked in #9. #8 should feed that policy with a profile/book-scoped realtime candidate rather than implement a second resume policy of its own.
Relationship to existing work
Do not merge automatically.