How melihercan/webrtcme works
WebRTCme presents a W3C-like C# API over platform-specific WebRTC implementations. An application creates peer connections and media through that API; middleware adds media management, a video tile, and data/file messaging, while the connection package supplies signaling for peer-to-peer or mediasoup-SFU calls. The graph preserves these documented capabilities, plus the sampled MAUI rendering, recording, and mediasoup negotiation layers. Broad package relationships come from the README; sampled source confirms the finer implementation links shown.
Main entry points: Api W3C API · WebRTCme.Connection Connection Layer · Handler.cs Mediasoup Handler · WebRTCme.Bindings Native Bindings
Components 21
Unified WebRTC API
- W3C API
WebRTCme/Api - Platform Facade
WebRTCme/CrossWebRtc.cs
Platform Bindings
- Native Bindings
WebRTCme.Bindings - Blazor Interop
WebRTCme.Bindings/WebRTCme.Bindings.Blazor/Interops/JsEventHandler.cs
Call Middleware
- Media Managers
WebRTCme.Middleware/Core/Services - Data Manager
WebRTCme.Middleware/Core/Services/DataManager.cs - Media Recorder
WebRTCme.Middleware/Core/Services/MediaRecorderManager.cs - MAUI Video Tile
WebRTCme.Middleware/Maui/Media.cs - MAUI Tile Handler
WebRTCme.Middleware/Maui/Platforms/iOS/MediaHandler.MaciOS.cs
Connection Layer
- Connection Layer
WebRTCme.Connection/WebRTCme.Connection - Peer-to-Peer
WebRTCme.Connection/WebRTCme.Connection/Services - Mediasoup Handler
WebRTCme.Connection/MediaSoup/WebRTCme.Connection.MediaSoup/Client/Handler.cs - WebSocket Transport
WebRTCme.Connection/MediaSoup/WebRTCme.Connection.MediaSoup/ClientWebSockets/ClientWebSocketLitePcl.cs
Signaling Services
- Signaling Client
WebRTCme.Connection/Signaling/WebRTCme.Connection.Signaling.Proxy/Client/SignalingClient.cs - Signaling Server
WebRTCme.Connection/Signaling/WebRTCme.Connection.Signaling.Server/Program.cs
Other components
- Application
- Remote Peers
- Mediasoup SFU
- Browser WebRTC
- Native WebRTC SDKs
- Recorded Media
Connections 22
- Application → Platform Facade: uses
- Platform Facade → W3C API: exposes
- W3C API → Native Bindings: maps to
- Native Bindings → Browser WebRTC: wraps
- Native Bindings → Native WebRTC SDKs: wraps
- W3C API → Media Managers: extended by
WebRTCme.Middleware/Core/Services/DataManager.cs - Media Managers → Data Manager: includes
- Media Managers → Media Recorder: includes
- W3C API → MAUI Video Tile: renders streams
WebRTCme.Middleware/Maui/Media.cs - MAUI Video Tile → MAUI Tile Handler: mapped by
WebRTCme.Middleware/Maui/Platforms/iOS/MediaHandler.MaciOS.cs - MAUI Tile Handler → W3C API: reads tracks
WebRTCme.Middleware/Maui/Platforms/iOS/MediaHandler.MaciOS.cs - Media Recorder → Recorded Media: writes blobs
WebRTCme.Middleware/Core/Services/MediaRecorderManager.cs - Application → Connection Layer: uses
- Connection Layer → Peer-to-Peer: creates
WebRTCme.Connection/WebRTCme.Connection/Extensions/ServiceExtensions.cs - Connection Layer → Signaling Client: uses signaling
- Connection Layer → Mediasoup Handler: supports SFU
- Mediasoup Handler → W3C API: negotiates via
WebRTCme.Connection/MediaSoup/WebRTCme.Connection.MediaSoup/Client/Handler.cs - Mediasoup Handler → WebSocket Transport: uses transport
- Signaling Client → Signaling Server: signals
- Peer-to-Peer → Remote Peers: connects
- Mediasoup Handler → Mediasoup SFU: connects through
- Mediasoup SFU → Remote Peers: relays media