Nowadays, many developer service providers have instant messaging functions. I will list some similar functions of my SegmentFault partners. You can make some reference through their ideas
That’s true. All the things mentioned above can be used immediately.
If you want to play more deeply by yourself, you can simply use the pushed SDK and the problem of maintaining long links will be solved. You only need to implement the specific business logic code.
To be more technical, use web socket or mqtt, etc. These can also maintain long connections, but it will be more troublesome. For example, disconnection and reconnection, these situations need to be considered.
Use XMPP protocol or sip protocol. Currently there are many protocol stacks based on these two protocols. xmpp is a purely IM-oriented protocol. A complete instant messaging service must not only meet the functions required for instant messaging, but also There also needs to be certain expansions, such as friend management, group messaging, conference rooms, push messages for online and offline friends. As for the pictures, audio and video you mentioned, they are considered media information in instant messaging.
To save trouble, there are now a lot of cloud IM, but it only saves trouble in the early stage, and the later operation is not something you can decide by yourself. So just add a painless IM function, you can use cloud IM. In the long run, of course everyone wants to have their own IM technology, but it is not easy to develop it completely by yourself, but it is also more workload. Very big.
Open source China has an open source lightweight mobile instant messaging technology framework: http://git.oschina.net/jackjiang/MobileIMSDK, The documentation is also relatively complete: http://www.52im.net /forum-89-1.html, it may be worth knowing. It is a good thing for people who are learning IM development.
It is recommended to directly connect to the third-party IM cloud service. With the development of technology, it is no longer popular to reinvent the wheel, because the structure of the wheel is becoming more and more complex, and the requirements for functional and non-functional indicators are getting higher and higher; but our users will no longer wait for us. While we are still drawing the drawings of wheels, our competitors may have already built their cars and beat us to the Chang'an Avenue. If the IM function is required and the technical support is in place, you can directly call the NetEase Yunxin IM SDK and API to quickly realize the IM function http://netease.im/im
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
Nowadays, many developer service providers have instant messaging functions. I will list some similar functions of my SegmentFault partners. You can make some reference through their ideas
That’s true. All the things mentioned above can be used immediately.
If you want to play more deeply by yourself, you can simply use the pushed SDK and the problem of maintaining long links will be solved. You only need to implement the specific business logic code.
To be more technical, use web socket or mqtt, etc. These can also maintain long connections, but it will be more troublesome. For example, disconnection and reconnection, these situations need to be considered.
Use XMPP protocol or sip protocol. Currently there are many protocol stacks based on these two protocols. xmpp is a purely IM-oriented protocol. A complete instant messaging service must not only meet the functions required for instant messaging, but also There also needs to be certain expansions, such as friend management, group messaging, conference rooms, push messages for online and offline friends. As for the pictures, audio and video you mentioned, they are considered media information in instant messaging.
Just use Rongyun or Huanxin, it is also very convenient to manage
Xinmaotong has a complete set of solutions and free integrated interfaces. It is very convenient to use.
http://www.semot.com/im/
To save trouble, there are now a lot of cloud IM, but it only saves trouble in the early stage, and the later operation is not something you can decide by yourself. So just add a painless IM function, you can use cloud IM. In the long run, of course everyone wants to have their own IM technology, but it is not easy to develop it completely by yourself, but it is also more workload. Very big.
Open source China has an open source lightweight mobile instant messaging technology framework: http://git.oschina.net/jackjiang/MobileIMSDK,
The documentation is also relatively complete: http://www.52im.net /forum-89-1.html, it may be worth knowing. It is a good thing for people who are learning IM development.
It is recommended to directly connect to the third-party IM cloud service. With the development of technology, it is no longer popular to reinvent the wheel, because the structure of the wheel is becoming more and more complex, and the requirements for functional and non-functional indicators are getting higher and higher; but our users will no longer wait for us. While we are still drawing the drawings of wheels, our competitors may have already built their cars and beat us to the Chang'an Avenue. If the IM function is required and the technical support is in place, you can directly call the NetEase Yunxin IM SDK and API to quickly realize the IM function http://netease.im/im