ejabberd 2.0.0: PubSub, PEP, Proxy65, HTTP-Bind...

Submitted by badlop on Wed, 2008-02-20 20:52

ejabberd 2.0.0 was finally released. Check the announcement for details and download links.

It has been 15 months since the last ejabberd release that included new features or improvements. This means that ejabberd 2.0.0 includes a large number of new features, improvements and bugfixes. Just to name a few: more clustering features, updated Pub-Sub service with PEP support, file transfer proxy, integrated HTTP file server, HTTP binding, and PAM authentication.

Please read with detail the Release Notes for a list of changes and important notes.

Source code and binary installers are available as usual in the ejabberd downloads page.

To formally report bugs please use the ejabberd bug tracker. Alternatively, you can start a discussion in the ejabberd mailing list or in the ejabberd forums.

Has ejabberd community a otp release?

Submitted by xeodon on Thu, 2008-05-08 12:51.

Is there ejabberd as the OTP release?
Can i start target system with ejabberd and then updrade it as a general OTP system?

xmpp virtual s2s transports?

Submitted by Manuel Mely (not verified) on Tue, 2008-03-18 16:20.

Ejabberd dev core team had think about supporting virtual s2s transport? The idea is to proxify s2s connections from xmpp servers that can't exchange messages with internet, so they can do this throught my s2s ejabberd proxy :) .
I'm playing with NAT and some SRV records, it must work, but is a little bit tricky to configure if i have lot of xmpp domains.

Cheers.

Did you check s2s_proxy

Submitted by badlop on Wed, 2008-03-19 20:51.

Did you check s2s_proxy patch for ejabberd? Does it provide the functionality you want?

s2s_proxy patch

Submitted by Michael Gruener (not verified) on Wed, 2008-04-02 07:20.

Does this patch still work with ejabberd 2.0? And have the problems regarding S2S with Gtalk been fixed?

s2s_proxy doesn't apply cleanly to 2.0.0

Submitted by badlop on Sat, 2008-04-05 18:49.

Michael Gruener wrote:

Does this patch still work with ejabberd 2.0?

It was written for 1.1.3, and the s2s code got several changes in 2.0.0, so it doesn't apply cleanly. It would require to be adapted. I could try in the next weeks.

s2s_proxy patch adaption

Submitted by Michael Gruener (not verified) on Mon, 2008-04-07 08:26.

badlop wrote:

Michael Gruener wrote:

Does this patch still work with ejabberd 2.0?

It was written for 1.1.3, and the s2s code got several changes in 2.0.0, so it doesn't apply cleanly. It would require to be adapted. I could try in the next weeks.

It would be really nice to see this patch working again with ejabberd 2.0.0 :)

Michael Gruener, does this

Submitted by Manuel Mely (not verified) on Mon, 2008-04-21 12:49.

Michael Gruener, does this patch works fine for you?
I tried this patch on ejabberd 1.1.3, it works but i had some messages looses.
It will be nice if some erlang guru :), could fix this module, and even better... make it a built-in module on ejabberd 2.0.x release. Is this so difficult to do??

I've updated the s2s-proxy

Submitted by badlop on Tue, 2008-04-22 10:44.

I've updated the s2s-proxy patch to ejabberd 2.0.0. I didn't test it.

I really like the good

Submitted by Anonymous (not verified) on Tue, 2008-03-04 10:53.

I really like the good readable log files :)

Support for 1.1.x

Submitted by tlaramie on Fri, 2008-02-22 13:05.

Has support / bugfixes for 1.1.x on the SVN ceased with the release of 2.x or will some manner of updates still make it's way over to that trunk?

Support for 1.1.x: only critical bugs

Submitted by badlop on Mon, 2008-02-25 01:00.

tlaramie wrote:

Has support / bugfixes for 1.1.x on the SVN ceased with the release of 2.x or will some manner of updates still make it's way over to that trunk?

2.0.0 has new features, bugfixes... and bugs over 1.x. The effort right now is in stabilizing the 2.0 release line, fixing bugs for 2.0.1. This will make 2.0 an acceptable target for conservative 1.1 servers.

I asked, and the 1.1 release line will get support for critical bugs for quite some time. But it isn't planned to introduce new features, improvements or fix smaller bugs that don't compromise the server.

Did I understand correctly your question? Do you have any comment?

Nope that's perfect

Submitted by tlaramie on Wed, 2008-02-27 12:08.

We just rolled out a new cluster based on 1.1 so it'll be awhile before we move on to 2.0 until I get a chance to benchmark it and confirm that it runs on the hardware.