Relationship between Libjingle and various protocols

1. Introduction to related Protocols & middot; XMPP protocol (core protocol): TheExtensibleMessagingandPresenceProtocol, which can expand the communication and representation protocols. To put it bluntly, it defines the protocol for transmitting data of a specified node based on XML streams. The advantage of doing so is to unify... "/> <scripttype =" text/jav 1. Introduction to relevant protocols-XMPP Protocol (core Protocol): The Extensible Messaging and Presence Protocol extends communication and representation protocols. To put it bluntly, it defines the protocol for transmitting data of a specified node based on XML streams. The advantage of doing so is unification (peakflys note: According to this definition, everyone can communicate and communicate with each other. This should be very promising !). It is an open and scalable protocol, including the Jingle protocol, which is an extension of the XMPP protocol. (Peakflys Note: Earlier versions may not be able to find this protocol when Wireshark is used to capture packets. in this case, you can select Jabber, the predecessor of XMPP ). At present, many IM programs are developed based on the XMPP protocol, including gtalk. · Jingle protocol (important protocol): Jingle protocol is an extension protocol on XMPP protocol. it solves the point-to-point connection problem under the XMPP protocol framework, that is, P2P connection. In the Jingle framework, users can establish connections even under firewall or NAT network protection to provide file transfer, video, and audio services. Programmatic file is XEP-0166 TURN protocol: Full name: Traversal Using Relays around NAT, as the name suggests, is through the relay server to transmit data protocol. · STUN protocol: Simple Traversal of UDP over NATs, that is, nat udp Simple Traversal, which allows clients located after NAT (or multiple NAT) to find their own public network addresses, find out which type of NAT you are located and the Internet port that NAT is bound to a local port. P2P is much more convenient if you know the NAT type and have a public IP address and port. · ICE protocol: Full name: Interactive Connectivity Establishment, that is, Interactive connection Establishment. to put it bluntly, it is the most suitable connection using protocols such as STUN and TURN. 2. relationship between Libjingle and various protocols: the initiator of the Jingle protocol is Google, while the libjingle Library is also implemented by Google. The ICE protocol is basically included in the Jingle protocol, therefore, you only need to know the differences between libjingle and Jingle protocols. History of www.2cto.com: Libjingle is probably created at the same time as the jingle XMPP extension. The Libjingle team established their own protocol to handle session negotiation and then worked with standardized jingle (based on XMPP Standards. Although jingle and libjingle are very similar, they are different and cannot be used together. The source code version of libjingle still uses the original network protocol, which is slightly different from the previous one and cannot be compatible with the jingle specifications. However, it is close enough to jingle, so it is worth learning jingle's manual. Similar to "close but not the same", libjingle's video content description (early jingle's video content description format XEP-0167), ICE's transfer description (early jingle's ICE transfer XEP-0176 ), and the UDP description of the stream (early jingle stream UDP transmission description XEP-0177) III. related documents: RFC3921 (Download: RFC3921) core documents of XMPP protocol RFC3489 (STUN) (download: RFC3489) STUN protocol draft rfc5245 (ICE) (Download: RFC5245) ICE protocol draft xep-0166 (Jingle) (Download: XEP-0166) Jingle protocol official subject document xep-0176 (Jingle ICE-UDP) (Download: XEP-0176) official document defining the combination of Jingle and ICE (mainly to redescribe the ICE protocol using XMPP as the ICE Channel)