HTML Refresher and Detailed Study - Part 14
Last updated on 14 June 2026 Post series: Part 1 , Prev Part (13) , Post Series TOC Contents (sections and/or jump links) Stage 8: Cloud client deployment of Delayed uppercase chat app; Some server changes Client deployment to Netlify Internet being down and so Cloud server being unreachable does not trigger Offline event as LAN is still up Client ws.send() does not report error if LAN is still up but Internet is down and server is unreachable Windows OS actively probes Internet connectivity for its Taskbar Internet online/offline status icon WebSocket timeout varies for Idle Tab and Active Tab (has outstanding message(s)) WebSocket API does not have mechanism to check if message is received by server; Application-Level Acknowledgements; Watchdog Timers Changing Server duplicate clientId handling to Last-In Wins Testing Last-In Wins approach on server Stage 8: Client refactoring with Outbox pattern to fix lost user messag...