Client and server need to talk

on YouTube ↗30m

" summary

Shows how to make client and server actually stay in sync: implements a simple counter implemented for collaborative edits, compares XMLHttpRequest, long‑poll and WebSocket subscriptions, and uses server time correction to avoid surprises. Describes conflict frequency (many conflicting updates within the first 100 ms), offline‑first reconciliation, and a working strategy that uses a server time endpoint (Firebase/open server time mentioned) plus versioned operations so merges succeed in practice. Includes code‑level concerns and what fails in naive approaches.

AI-written summary · about

" chapters (7)

1. 0:00Real-time web apps intro
2. 5:14Server-client challenges
3. 10:57Data sync philosophy
4. 16:13Conflict handling
5. 21:47Offline-first trade-offs
6. 25:12Real-time updates abstraction
7. 27:09Q&A

" related talks

• 01h 20mEfficient Client-Server Communication with Differential Synchronization and JSON PatchBrian Cavalier · SpringOne2GX 2014
• 25mTaming Client-Server CommunicationScott Andrews · JSConf US 2013
• 53mThe Client and Server Need to TalkNikita Prokopov · РИТ++ 2017
• 01h 18mThe future of chatGuillermo Rauch · JSFoo 2015
• 30mWebSockets: The Real-Time AvengersHarshil Agrawal · CityJS New Delhi 2024
• 29mWebSockets Bring Light at the End of the TunnelJoel Lord · NodePDX 2016
• 44mReal-Time Multi-User State Management for the Collaborative WebMatt Hayes · OpenJS World 2023
• 34mLogux, a new approach to client-server communicationAndrey Sitnik · React London 2017