[erlang-questions] Jabber Client

Mickaël Rémond <>
Wed Dec 13 09:16:16 CET 2006


Hello Darrin,

Le 13 déc. 06 à 04:57, Darrin Thompson a écrit :

> I'd like to access ejabberd from a web app.
>
> The options I've seen so far include jabberlang, and writing some kind
> of ejabberd module.
>
> I require anonymous logins, and ability to run on amd64 and x86.
>
> Is jabberlang up to the client side of this? If so, where are the
> official binaries? Jabberlang is broken in cean. The build system in
> svn seems incomplete. Where are all those shared objects coming from?

Jabberlang for now rely on ejabberd. You need ejabberd to use it. The  
shared object you are mentionning comes from ejabberd.
That said Jabberlang is a client library that rely on a server  
implementation which seems strange.
That's why we are currently doing some code refactoring.
Our target is to have:
- exmpp: A common XMPP library that is used by ejabberd and Jabberlang
- Jabberlang: Relying on exmpp.
- ejabberd: Relying on exmpp.

We are in the middle of this refactoring currently.
A partner/customer has contributed a reworked exmpp module that we  
are integrating into both Jabberlang and ejabberd.

The Jabberlang API will not change in the first step, but once this  
has been done we will work on improving it.

> Another possibility would be just writing an ejabberd module which can
> bridge for clients. Is there some example code for this somewhere?

Yes, there are plenty of example:
- in ejabberd itself. ejabberd is modular and many parts are  
developed as module.
- in the brand new ejabberd-modules repository that we have opened to  
allow contributors to work together.
See Process-one forge: https://forge.process-one.net/browse/ejabberd- 
modules
and SVN: https://svn.process-one.net/ejabberd-modules/

If your module if of general interest, it might be relevant at the  
end to put it in the ejabberd-modules SVN.

I hope this helps,

-- 
Mickaël Rémond
  http://www.process-one.net/


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20061213/f3de9827/attachment.html>


More information about the erlang-questions mailing list