By: Survey results: and the WebRTC developers say... | webrtcHacks
[…] without some backend development somewhere (notable exception with the Serverless WebRTC project here). You can XaaS it from someone else but that generally implies some cost. This could mean...
View ArticleBy: Wenli
Hi, Chris! Thanks for sharing! I checked out the example and it sounds really inspiring that even local server is unnecessary for WebSocket connection. But I tried the examples on Chrome for Android...
View ArticleBy: cjb
Hi Wenli — I actually hadn’t tried out Chrome on Android so I’m not sure why it’s failing. Let me know if you figure anything out, thanks!
View ArticleBy: Xiang Li
Hi Chris, Thank you for your amazing work! I am trying to build a LAN webrtc instant message application. It seems to me it can only do 1 on 1 connection cause there is no option to add new client...
View ArticleBy: PB
I love this! I am new to WebRTC and have been looking for a solution without a signalling server. Your code is a gawd send. I do have a couple of questions: 1. I would like to jump on Xiang Li’s...
View ArticleBy: Vojtěch Sázel
I just made similar demo also as an Android app. It’s compatibile with your demo. Check it out there: https://github.com/wojta/serverless-webrtc-android
View ArticleBy: Chris
This is really cool but I’m wondering if you have any idea how you can have a fixed offer? So for example if I wanted to set up two clients to communicate only once, and store their offers, so that...
View ArticleBy: cjb
No, it’s not possible. Part of generating the offer involves doing a “holepunch” in the NAT so that there’s actually an open port on the client’s router that will get to them, and as I understand it...
View Article
