Openfire compared to ejabberd

We have been using Openfire for the past few years and the one thing we cannot get successful is having SSL working. Another which openfire does not offier is multi-host domains. This has been in the works for a few years.

I am not familar with ejabberd. What is the benefits working with ejabberd compare to openfire? Does it come with live chat and ssl connection? connect to public gateways like msn? desktop and web apps like spark and sparkweb?

Would love to hear what is the difference between the two. Currenly we are using openfire 3.6.3.

Quote: What is the benefits

Quote:

What is the benefits working with ejabberd compare to openfire?

This aren't direct differences or benefits, not an exhaustive list, just some generic points I consider nice:

  • Low CPU consumption. All design decisions when developing ejabberd always care first about computational performance.
  • Stability: clients may crash, the program may have bugs, but in any case the server keeps running for the other users.
  • Primarily configured using config file
  • Simple WebAdmin for managing users, modules, ...
  • Clustering support: install ejabberd in several machines, setup them as a cluster and let the client load spread among them
  • ejabberd commands (to manage the server, accounts, rosters, MUC, Vcard, ...) can be called using shell program, XMLRPC, or REST.
  • Contributions: there are many other features available as contributed modules
Quote:

Does it come with live chat

I don't know what 'live chat' means.

Quote:

and ssl connection?

Yes, ejabberd supports both the old SSL and the new STARTTLS. I'm almost sure Openfire also supports both of them, because all XMPP servers support at least the new STARTTLS encryption.

Quote:

connect to public gateways like msn?

ejabberd doesn't include transports/gateways. You can install XMPP gateways (for example Spectrum) in the same machine and connect them to ejabberd (some tutorials).

Quote:

desktop and web apps like spark and sparkweb?

ejabberd doesn't include XMPP clients. If spark and sparkweb are XMPP clients, then they will work with ejabberd, like any other desktop or web XMPP clients.

Quote:

I am not familar with ejabberd.
Would love to hear what is the difference between the two. Currenly we are using openfire 3.6.3.

You can install ejabberd in your personal machine, just for playing and testing it.

Later in some days/weeks, if you finally decide any migration to ejabberd or any other server, it would be useful for ejabberd developers and other wanabee-migration-admins if you comment in this thread what did you decide and why.

For example, I'm curious what will be your opinion on Tigase (a Java server, like Openfire).

Syndicate content