ejabberd - Comments for "Migration issues from XMPP client bot to XMPP component bot"

The bot can send unsubscriptions, and later subscriptions

mfoss — Wed, 15 Apr 2009 12:39:51 +0000

hip10 wrote:

Yes. There are two ways to alleviate the migration for users:

A) Before stopping the old bot, it could send unsubscription notices to all his contacts. Later the new bot could request subscription to those users that you know are interested in the service. To know how to implement this in your bot, you can check XMPP protocol documentation, and your XMPP library.

B) If all the users of your bot are in your Jabber server, you could modify the roster items stored in the database, changing the JIDs of the old bot to the new bot. This would require understanding the format of the database tables, and the format of ejabberd database is not documented.

client subscription

hip10 — Mon, 13 Apr 2009 15:09:44 +0000

Thanks for the reply. But in the case of the client, the user will need to unsubscribe from an existing client bot, and subscribe to a new component bot since the address is different, right? E.g. client bot=>movies@hip10.net, component bot=>movies@movies.hip10.net (assuming that one server can host multiple component bots, which means that we need to distinguish via subdomains, right?)

No need to restart

mfoss — Mon, 13 Apr 2009 11:55:31 +0000

hip10 wrote:

If we add more and more component bots in the future, do we need to shutdown ejabberd and restart the server every time there is a new component bot?

In ejabberd, a component is managed by an ejabberd_service listener. Listeners in ejabberd are either defined in ejabberd.cfg, or started using the ejabberd Web Admin. So no need to restart: you can add start components, and add ejabberd_service listeners using the Web without restarting ejabberd.