Messenger development

Question

Messengers

I want to try to write my own icq / jabber messenger, the client part on html5 / js. What would you recommend to take as a server part? Where can I read about how the server side is designed and implemented?

Answer 1

There is no particular choice, it is either ejabberd, openfire or tigase. You can look here: en.wikipedia.org/wiki/Comparison_of_XMPP_server_software
The first one is the most common. It's fast, parallelizes nicely (it's written in erlang for a reason) and supports a very large number of HEPs. The main drawback is that few people know erlang)
Openfire is a convenient setup, all sorts of guis and so on, but performance sags heavily under heavy load. Ideal for small networks.
tigase - just like openfire, it is written in Java, but it scales much better, and in general it is written with an emphasis on performance. On the other hand, the last time I looked at it, it supported far fewer goodies and there were problems with the documentation.
About what to read -www.ejabberd.im/ www.igniterealtime.org/projects/openfire/ www.tigase.org/
There is quite detailed documentation, mail lists and sources, the last one is perhaps the most useful)
In general, it’s not very clear why you need a server part if you write client.

Answer 2

Unsubscribe only for XMPP.
You can do without the server part and implement everything on the client. This is where Strophe.js
comes in. If the choice is to hide most of the logic in the server, the implementation lends itself very well to NodeJS with its event-driven approach. In this case,
node-xmpp will become indispensable around which you can build your own implementation, or extend node-xmpp-client

Answer 3

If anyone has a desire to test a new and completely secure SafeUM messenger, we will be very happy. You can even win a premium for a whole year!