From http://mysuperbaby.iteye.com/blog/904566
Project and source code location
Http://code.google.com/p/libjingle/
Developer guideline location
Http://code.google.com/apis/talk/libjingle/
Why study this? For the following considerations:
- Now an important aspect of XMPP protocol is voice/video chat and file transfer, and its corresponding XMPP extension protocol is mainly jingle (XEP-0166
Http://xmpp.org/extensions/xep-0166.html) and a series of other jingle-based protocols.
- The jingle extension protocol was contributed by Google to the xsf Foundation. Currently, it is in the draft status and has not been officially locked down.
- The voice/video chat and file transfer protocols of the goolge talk client are similar to the jingle protocol, but they are different from the jingle protocol. google has also opened up the implementation of this Protocol, that isLibjingle. Google almost submits the jingle protocol to xsf while making libjingle open-source.
- Therefore, the XMPP jingle protocol is similar to the libjingle protocol, but it is not compatible. currently, many XMPP clients (such as spark, PSI, and pidgin) basically implement the jingle protocol, but Google Talk clients also use the Protocol in libjingle. this means that these XMPP clients cannot transfer files with Google Talk clients.
- Currently, the main public XMPP service providr is goolge talk. Therefore, to develop a competitive XMPP client (especially on the Android platform), in addition to implementing the Standard jingle protocol, it is better to implement the Protocol in libjingle to transfer files with the Google Talk client.
- Libjingle is developed in C ++, so if you want to porting it to the Android platform using Java, you still needCodeFor some research.
