ejabberd - Comments for "Erlang client vs Ejabberd module"

I'll go with an ejabberd

Ted — Tue, 05 Aug 2008 21:41:44 +0000

I'll go with an ejabberd component.

Thanks.

Check this: Thoughts On Scalable XMPP Bots

mfoss — Mon, 04 Aug 2008 19:42:56 +0000

Ted wrote:

Is there any advantage of a jabber client compared to ejabberd module?
It seams like an ejabberd module will be more scalable out of the box and will benefit from the ejabberd api power.

There is a recent blogpost on this topic: Thoughts On Scalable XMPP Bots

I imagine a Jabber component

mfoss — Fri, 01 Aug 2008 16:40:29 +0000

I imagine a Jabber component would be more scalable that a Jabber client bot.

In my previous comment I mentioned both alternatives because you asked about both :)

Is there any advantage of a

Ted — Sun, 27 Jul 2008 23:55:38 +0000

Is there any advantage of a jabber client compared to ejabberd module?
It seams like an ejabberd module will be more scalable out of the box and will benefit from the ejabberd api power.

Writing a Jabber client bot seams like a very hard task while building a bot from ejabberd module seams achievable.
Am I missing something?
Will an ejabberd module bot be able to interact with thousands of simultaneous users, perform simple logic and interact with a database?

Thanks

Look at existing Jabber bots; or for example mod_chatcommands

mfoss — Sun, 27 Jul 2008 14:25:50 +0000

You can write your bot as a Jabber client using any programming language. Or extend an existing bot with the features you want, for example there is Neutron written in Python. There isn't yet any stable XMPP client library written in Erlang.

Or you could write your bot as a Jabber component. In this case you can implement it in an ejabberd module, for example look at mod_chatcommands.