XMPP protocol for instant messaging underlying writing (zero)-nonsense and preparation before the beginning, xmpp instant messaging
I want to write a summary for a long time, but I have been busy and have no time to calm down and do such a thing.
I once told my eldest brother Qin that I didn't have the open source spirit, but because there were too many things and I didn't have time to write a blog. I didn't quite understand it at the beginning. Only when I was in this position could I understand the mood of my eldest brother Qin and how depressed he was about me. Okay, let's get down to the point. Let's talk about XMPP.
1. literal understanding of XMPP
Xmpp Chinese name: Extensible communication and representation Protocol, English name: Extensible Messaging and Presence Protocol. I will not talk much about the specific definition. Well, I admit that this is the answer given by Baidu encyclopedia, although it is a bit difficult to understand, however, I still hope that there is no IM Foundation. You can check the definition of Baidu encyclopedia before you implement XMPP-based IM (Code-related IM can be skipped and useless, however, it is helpful for students who are not good at English.
Key: Extended extensible, presence, protocol.
In this definition, we hope you will keep these three description keys in mind. Yes, it should be back to the stream, because the English documents connected are the articles around these three keys.
2. Learn and read XMPP
If you want to become a stranger or a big brother such as Twitter, learning and reading the official website is the only way out.
Official Website: http://xmpp.org/Where do not know here, the source of all evil (because you need to read these dense English characters for a long time)
Http://wiki.jabbercn.org if you really have bad English, this has a Chinese.
In fact, the monks don't want to post Chinese translation. It's not that I pretend to be forced (reading English, reading English documents is high, high handsome and rich). It's a bloody lesson that tells me to tell you, who is the MLGB Chinese translation website that let me watch! Cao! After reading the Chinese document, I need to refer to the Chinese document repeatedly and find the English version of the official website three times. It is so hard, because the variable nouns given by Chinese characters are so hard to understand by TMD and are not as good as the English description. In particular, various rules, such as configuration, relationXEP, client-side notes, and server-side notes, are not very well handled. Prepare a dictionary at any time and start working.
3. Preparations
After server a is set up, you can work. (This is inexperienced, and it is difficult to mislead everyone with pure client food)
B. Read the RFC once.
Okay. Rome is not created in one day. You can do nothing today, just watch RFC6121.
If your manager scolds you and urges you, you can use your humble friend's words with confidence:
For reprint, please sign the source. Thank you :)
Original article Portal
Eldest Brother, this is really difficult... It takes two days to read this RFC6121 to write this blog. I can only watch it for one day. I will start writing code tomorrow.
Btw: If you really cannot understand RFC6121, you can give up writing core IM, and the speed behind you will be at least three times slower than those who understand this RFC. Do not think this is easy or unimportant. Of course, you may not listen to my advice, but hope that there will be no errors or inexplicable problems when the project is going to be launched soon.
Btw2: XEP is not critical to RFC
Btw3: Search for whosv in IOS client appstore Based on xmppFramework. Try it out (Versions later than 2.0.3 are not maintained by me. Yes, I quit ).
Btw4: next release notice