I'am not sure i understand what you mean: do you mean we should use webRTC for the whole source client, streaming server, end users clients?
As there is already a lot of media client that implement playing from HTTP streams, this would involve a lot of work. We thought it may be easier to keep those clients untouched and just leverage webRTC to allow to source the stream from any browser, using a gateway that translate the webRTC streams to icecasts ones. But maybe I just completly misunderstood your point ? Thanks for you answer anyway, and sorry for the delay of mine. :) Le 04/07/2014 20:21, Martin Thomson a écrit : > Have you considered just using WebRTC? The gateway would have to decrypt and > re-encrypt, but that's all. It's probably much easier to do (you wouldn't > have to perform all the nasty receiver-side logic in the gateway to deal with > PLC and all that mess, for instance). > > ----- Original Message ----- > From: "Mathieu Goessens" <[email protected]> > > [...] translate webRTC streams [...] > _______________________________________________ > dev-media mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-media > -- Mathieu Goessens IT consultant. [email protected] + 33 6 07 91 54 87 http://gebura.eu.org
signature.asc
Description: OpenPGP digital signature
_______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
