diff --git a/README.md b/README.md index fd29e1f..39654d0 100644 --- a/README.md +++ b/README.md @@ -49,7 +49,7 @@ server/ Node.js backend: proxies ALL Emby access (auth, catalog, src/index.js Express app + REST endpoints src/embyAuth.js server-side login against Emby + session cookies src/embyProxy.js generic Emby request/response proxying (incl. HLS) - src/wsHandler.js WebSocket protocol (see comments in the file) + src/socketHandler.js Socket.IO protocol (see comments in the file) src/partyManager.js in-memory room state client/ Static frontend (plain JS, ES modules, no build step). @@ -57,7 +57,7 @@ client/ Static frontend (plain JS, ES modules, no build step). js/shell.js persistent sidebar + #mainContent the router swaps js/tiles.js poster-tile rendering shared by home.js and library.js js/embyApi.js calls our own /api/* routes (auth, catalog, playback options) - js/party.js our own backend's party REST + WebSocket client + js/party.js our own backend's party REST + Socket.IO client js/views/ one file per screen: login, home, library, series, player src/WatchParty/ The earlier Emby-plugin attempt. Builds fine and installs, @@ -100,6 +100,9 @@ Then put it behind your existing reverse proxy like everything else - [x] Proxy all Emby access server-side; Emby-themed UI (sidebar, carousels) - [x] TV show navigation (Series → Seasons → Episodes) + episode auto-queue - [x] Player language/subtitle/quality pickers +- [x] Socket.IO instead of raw WebSockets; fixed two real memory leaks + (dead-connection cleanup server-side, view teardown on navigation + client-side) — see docs/architecture.md - [ ] Try a full party end-to-end with two real accounts (still the main gap) - [ ] Music: dedicated player, artist/album browsing, collaborative playlist - [ ] Tune transcoding target / support direct play when possible diff --git a/client/index.html b/client/index.html index c31f550..14f2f67 100644 --- a/client/index.html +++ b/client/index.html @@ -6,6 +6,7 @@