← Back to context

Comment by written-beyond

21 days ago

Oh no I didn't meant a write about the prompting I meant about the actual client you wrote.

What was the final framework like, how did the protocols work, etc.

Oh, there's a centrally hosted web server that hosts the assets, some of the conference state, account info, that sort of thing. Clients join a SSE channel for notifications of events relating to other clients. Then a combination of POST to the web service & ICE and STUN to establish all-to-all RTP over WebRTC for audio, and other client state updates as JSON over WebRTC data channel. The UI is very specific to the app but built on winit, webgpu, and egui. wry for embedded browser.