Websocket

Disclaimer: This blog post is automatically generated from project documentation and technical proposals using AI assistance. The content represents our development journey and architectural decisions. Code examples are simplified illustrations and may not reflect the exact production implementation. The Biometric Challenge Caroline had a question that changed everything: “What if we could track heart rate during pressure points?” I looked up from my keyboard. “You mean correlate biometric data with match events?” “Exactly,” she said. “We already track every shot, every score change. If we add heart rate and movement data, we could see exactly when players get stressed.” Claude liked the idea: “Biometric data would let you detect fatigue patterns, recovery rates, momentum shifts—all based on actual physiology, not just scores.” We needed a system that could handle high-frequency data (up to 50Hz for gyroscopes), stream it in real-time from wearables, and correlate it with our existing event sourcing system. ...

Disclaimer: This blog post is automatically generated from project documentation and technical proposals using AI assistance. The content represents our development journey and architectural decisions. Code examples are simplified illustrations and may not reflect the exact production implementation. Table of Contents The Connection Problem Singleton Connection Managers Channel-Based Message Routing StreamConnection Implementation EventConnection Implementation Component Integration Server-Side Changes Results and Benefits Key Learnings The Connection Problem When Caroline and I were building the recorder page for Scores, we noticed something alarming: each web component was creating its own connection to the server. The audio recorder had a WebSocket, the manual input component had another WebSocket, each of the four biometric monitors had their own WebSocket, and the score dashboard, match highlights, and real-time updates each had EventSource connections. ...

Disclaimer: This blog post is automatically generated from project documentation and technical proposals using AI assistance. The content represents our development journey and architectural decisions. Code examples are simplified illustrations and may not reflect the exact production implementation. Table of Contents The Security Challenge OAuth2 Token Exchange Architecture Token Types and Lifetimes Delegation Chain with Act Claims WebSocket and SSE Integration OpenID Discovery and JWKS Key Management and Rotation Key Learnings The Security Challenge When Caroline and I were designing security for Scores, we faced a tricky problem: how do you securely authenticate WebSocket and Server-Sent Events connections without exposing tokens in URLs or requiring users to re-authenticate constantly? ...