How johni0702/mumble-web works
Main Components
a) Client-Side Components (Browser):
• HTML5 Frontend (from app/index.html)
• WebSocket Client
• WebRTC Audio Handler
• Worker Thread (from worker.js)
• Theme Engine (from theme.js)
• Localization System (from loc.js)
b) Server-Side Components:
• WebSocket Server
• WebRTC Handler
• Mumble Protocol Adapter
c) External Systems:
• Mumble Server
• Web Server (NGINX/Caddy)
• Matrix Integration (optional component)
Connection Flow
• Secure WebSocket connections (WSS) from browser to web server
• WebSocket connection from web server to mumble-web-proxy
• TCP/UDP connection from mumble-web-proxy to Mumble server
• WebRTC media streams (when available)
• Fallback audio path using WebSocket when WebRTC is unavailable
Specific Implementation Details
• Supported codecs (Opus for WebRTC, Opus/CELT Alpha for fallback)
• Configuration flow (config.js -> config.local.js)
• Theme system (MetroMumbleLight/Dark)
• Localization files (en.json, de.json, etc.)
Technical Details
Annotations for:
• Port numbers (64737 for WebSocket, 64738 for Mumble)
• Supported protocols (WebRTC, WebSocket)
• Security layers (SSL/TLS termination at web server)
• Codec support limitations
Component Relationships
Clear relationships between:
• Frontend and worker thread communication
• Theme engine and UI components
• Localization system and UI elements
• WebRTC/WebSocket fallback mechanism
For the Matrix integration, create a separate "Matrix Mode" view showing how the widget interfaces with the main application components.
Remember to include a version indicator and any relevant build/deployment information from the webpack configuration, as this will be important for understanding how the system is assembled and deployed.