[Server-devel] [ejabberd] Custom roster behaviour without writing your own mod_roster

[Martin Langhoff]

Mickael, Christoph,

thanks! Excellent pointers. A couple of followup questions...

On Thu, Nov 6, 2008 at 5:14 AM, Mickaël Rémond
<mickael.remond at process-one.net> wrote:
> Using mod_roster_odbc should work very well in your case. I would use that
> approach.

 - How many DB queries does mod_roster_odbc make? What factors control
their frequency? (I just know how often the clients query ejabberd
about their own roster either)

On Thu, Nov 6, 2008 at 5:23 AM, Christoph Mewes
<christoph.mewes at freiheit.com> wrote:
> Just because somebody advocated on the first option. This works pretty well
> through mod_xmlrpc as well. So it's more or less up to you. :)

That's encouraging too - sounds like using xmlrpc gives us a fairly
complete API and keeps ejabberd using mnesia (which is probably
faster, more efficient than talking to PostgreSQL via ODBC).

- Is mod_xmlrpc an official module now or is it still unofficial?
- Is it possible to make it listen on a socket rather than on a port?
I don't want any user in the server to be able to connect to it!

cheers,



m
-- 
 martin.langhoff at gmail.com
 martin at laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff