W3C home > Mailing lists > Public > public-webrtc@w3.org > March 2013

Re: Client/server (non-p2p) video

From: cowwoc <cowwoc@bbs.darktech.org>
Date: Sat, 30 Mar 2013 23:48:25 -0400
Message-ID: <5157B209.2010200@bbs.darktech.org>
To: public-webrtc@w3.org

     I second Kevin's motion. We need a more thorough discussion of how 
to model a client-server chat, especially in light of the fact that this 
is needed for multi-party chat (ideally you one the server to act as a 
gateway for the conversation, otherwise you end up with N-N links).

     Node.js is great and all, but I don't plan on using it to run in 
production. I'm looking for a solution that will allow me to run a 
single server that will handle both normal web content, and WebRTC 
streams. Running two separate servers is not ideal. Are there plans to 
offer better integration for Java-based web servers who wish to act as 
WebRTC peers?

Thanks,
Gili

On 30/03/2013 7:40 PM, piranna@gmail.com wrote:
>> The abstraction there is great, but from my understanding all the pieces weren't available yet for a one-to-many server using WebSockets - at least in any way that's not just using javascript to capture and send individual frames.
>>
> I have work with getUserMedia myself, I've been focusing on
> DataChannels, sorry... :-(
>
>
>> I'm more looking for the ability to do compressed streaming to a server. Currently the only way I can see this happening is to write a server that pretends to be a peer for WebRTC.
>>
> Why this would be bad? There are WebRTC libraries for Node.js, for example...
>
>
> --
> "Si quieres viajar alrededor del mundo y ser invitado a hablar en un
> monton de sitios diferentes, simplemente escribe un sistema operativo
> Unix."
>  Linus Tordvals, creador del sistema operativo Linux
>
Received on Sunday, 31 March 2013 03:49:43 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:33 UTC