You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Started the project with just voice calling. Would be nice to modularly allow having a larger interface that included receiving and sending chat messages. An extension of this would be to support mutli user chat.
The text was updated successfully, but these errors were encountered:
This client is xmpp based, using the jingle in libjingle. Let me explain a bit.
Jingle is xmpp based, and libjingle contains an implementation of jingle based on the spec, http://xmpp.org/extensions/xep-0166.html. To make things a little bit more confusing they also include an implementation of jsep(http://tools.ietf.org/html/draft-ietf-rtcweb-jsep-00#section-7.2) inside libjingle, which is what webrtc uses for media sessions, where webrtc is basically just glue and an audio/video processing library, and drivers.
In the end, I imagine libjingle might be swallowed up by webrtc, and broken into it's various parts and integrated, but it's a fair amount of code and probably not a top priority.
Started the project with just voice calling. Would be nice to modularly allow having a larger interface that included receiving and sending chat messages. An extension of this would be to support mutli user chat.
The text was updated successfully, but these errors were encountered: