Difference between Libjingle and WebRTC source code ?

[Lionel_RTC]

Hello folks,

I see there is two distincts projects for that, so I'm wondering what
is the main differences between the WebRTC source code (http://
webrtc.googlecode.com/svn/trunk), and the LibJingle implementation
(https://code.google.com/p/libjingle/source/browse/#svn%2Ftrunk%2Ftalk
%2Fapp%2Fwebrtc) ?

Is LibJingle taking all the WebRTC features in it (plus the "old"
Gtalk ones ?)

Thanks !
Lionel

[Ivan Vučica]

I believe standalone WebRTC library primarily delivers a more sensible API for the internal libjingle implementation. It is, of course, more sensible primarily in case you're evading XMPP, or at least the built-in XMPP implementation from libjingle; if you're just trying to deliver call functionality in the easiest way possible, and if you don't have your own XMPP framework, you'll probably like libjingle.

However, WebRTC is (as its name, you know, might suggest) also an API for use on the web, from Javascript. Library you're looking at is the code used in Chrome to deliver this functionality and Javascript-based API, as specified in various standards' drafts.

--
Ivan Vučica - iv...@vucica.net

[Zhihong GUO]

Hi Lionel,

WebRTC code in code.google.com only contains the video and audio codec, the RTP stack. The libjingle project contains the API of webRTC, it looks nurse but it's true. Besides, the libjingle has the stacks of XMPP and STUN, ICE implementation. If you want to make a total solution for VOIP, you have to build both.

BR

James

[Lionel_RTC]

Thanks for the awnsers !
I find it a little bit confusing. I think WebRTC should be a
dependency for the LibJingle project, not separate project :)

On Apr 17, 3:22 am, Zhihong GUO <gzhh...@gmail.com> wrote:
> Hi Lionel,
>
> WebRTC code in code.google.com only contains the video and audio codec, the
> RTP stack. The libjingle project contains the API of webRTC, it looks nurse
> but it's true. Besides, the libjingle has the stacks of XMPP and STUN, ICE
> implementation. If you want to make a total solution for VOIP, you have to
> build both.
>
> BR
>
> James
>
>
>
>
>
>
>
> On Monday, April 16, 2012 11:35:00 PM UTC+8, Lionel_RTC wrote:
>
> > Hello folks,
>
> > I see there is two distincts projects for that, so I'm wondering what
> > is the main differences between the WebRTC source code (http://
> > webrtc.googlecode.com/svn/trunk), and the LibJingle implementation
> > (https://code.google.com/p/libjingle/source/browse/#svn%2Ftrunk%2Ftalk

> > %2Fapp%2Fwebrtc<https://code.google.com/p/libjingle/source/browse/#svn%2Ftrunk%2Ftalk...>)

[PhistucK]

The LibJingle project exists long before WebRTC was even invented. It used to be an XMPP/GoogleTalk only stack, but a decision has been made to add additional network capabilities, while I believe WebRTC is mainly concerned the real time media aspect of the feature.

LibJingle is much more general and is also still used as an XMPP stack within Chrome (for example) for the Chrome Sync feature.

☆PhistucK