[Jingle] Proposed message to send to the IETF rtcweb and W3C WebRTC working groups.

Peter Thatcher pthatcher at google.com
Mon Jul 22 15:21:11 UTC 2013


On Mon, Jul 22, 2013 at 7:59 AM, Emil Ivov <emcho at jitsi.org> wrote:

>
>
> On 22.07.13, 16:28, Kevin Smith wrote:
>
>> On Mon, Jul 22, 2013 at 3:25 PM, Peter Thatcher <pthatcher at google.com>
>> wrote:
>>
>>> Why do you think Google has abandoned Jingle?  Every realtime
>>> application I
>>> know of at Google still uses Jingle for signalling.  In fact, here's the
>>> open source code the mobile apps (Google Talk and Google+ Hangouts) use:
>>> https://code.google.com/p/**libjingle/source/browse/trunk/**
>>> talk/p2p/base/sessionmessages.**cc<https://code.google.com/p/libjingle/source/browse/trunk/talk/p2p/base/sessionmessages.cc>
>>> .
>>> I can't show you the server-side code, but I have written much of it,
>>> and I
>>> can tell you it's still using Jingle for signalling.
>>>
>>
>> Peter,
>>    Thanks for this message -
>>
>
> Indeed this is helpful.
>
> How are you guys planning on migrating all of these to WebRTC's SDP and
> Offer/Answer? Are you thinking of mapping to Jingle in the browser? Or in a
> gateway?
>

Unfortunately, I can't comment on future product plans and implementation
details.  Sorry.


>
> Cheers,
> Emil
>
> --
> https://jitsi.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/jingle/attachments/20130722/a91658eb/attachment.html>


More information about the Jingle mailing list