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

2014/1/17 piranna@gmail.com <piranna@gmail.com>:
> 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
<ibc@aliax.net>