On Mon, Dec 6, 2010 at 12:16 AM, Jeffrey Ollie <jeff(a)ocjtech.us> wrote:
On Sun, Dec 5, 2010 at 8:38 PM, David Nalley <david(a)gnsa.us>
wrote:
>
> ejabberd is written in erlang, and appears to be one of the better
> supported xmpp server implementations. Aside from being written in
> erlang,
Erlang is actually a pretty interesting language, especially for
writing network servers. However there is the downside that I doubt
many people on the Infrastructure team are familiar with Erlang and
having some familiarity definitely helps out when configuring or
troubleshooting Ejabberd.
Yeah, that's my concern
> another downside is that it requires either postgres or mysql,
Where do you see this requirement? I'm not a ejabberd guru but as far
as I know ejabberd does not require postgresql or mysql, it will use
Erlang's built in database (MNESIA). The servers that I run at
$DAYJOB use LDAP as the user store and never touch a postgresql or
mysql server.
hmmm perhaps I read docs wrong then.
> Oddly enough I find myself leaning towards ejabberd, simply because it
> appears to be more robustly maintained. I have, in the past, used the
> 1.x version of jabberd (which is completely different) and ejabberd,
> as well as some others that aren't in Fedora atm.
Ejabberd is my preference too, but since I doubt I'll be able to do a
whole lot to help out don't let my opinion get in the way.
One other testimonial is that Facebook uses Ejabbed behind the scenes
to handle their chat service...
Yeah, I understand
jabber.org uses it as well now.
> Perhaps we can get this setup rapidly on a testing instance once we
> make a server choice.
Either Ejabberd or Jabberd2 are pretty easy to set up, at least in a
standalone single-node mode.