Re: Summary of "What is missing for building real services" thread

I'm not saying that W3C should publish a library to other to use, I'm
just answering to their question regarding if there's interest for a
WebRTC library to use outside browsers in so called "native"
applications, that definitelly there is.

2014/1/17 Iñaki Baz Castillo <>:
> 2014/1/17 <>:
>> As far as I know, yes, there's a lot of interest on using WebRTC
>> server-side and for native (non-browser) applications, so a native API
>> & bindings are being necesary. I know personally three companies (my
>> employer is one of them) having difficulties to work with native
>> WebRTC APIs, and from a personal perspectice, I'm interested on it so
>> I can be able to develop in-browser and server-side head-less WebRTC
>> applications using the same base code.
> There is also lot of interest in SIP and XMPP protocols and nobody
> expect to have a "unique code base for building SIP or XMPP
> devices/applications". Really, consider what you are proposing.
> If you want, start a project called
> "the-best-and-unique-webrtc-stack-written-in-my-favourite-language"
> and put it in Github with MIT license, but don't ask for such an
> aberration in W3C or IETF groups.
> I strongly propose to immediately stop this no-sense subject.
> --
> Iñaki Baz Castillo
> <>

"Si quieres viajar alrededor del mundo y ser invitado a hablar en un
monton de sitios diferentes, simplemente escribe un sistema operativo
– Linus Tordvals, creador del sistema operativo Linux

Received on Friday, 17 January 2014 17:00:47 UTC