Hi all,
I am trying to setup a shared roster group for our company's jabberd2 server that uses mysql as storage backend. Shared rosters are have been implemented since a patch [3] from 2004 in some way. The "ideas" page [1] lists shared roster groups as implemented for BDB and LDAP in mod_roster_publish. In [2], we get told that the normal storage - mysql - is used to retrieve the groups. [2] gives me hope that shared roster groups could actually work. Looking at the sources of mod_roster_publish [4] tells me that there are two tables: - "published-roster-groups" (field "groupname" is used from there) - "published-roster" (fields "jid", "group", "name", "from", "to" and "ask" are used) Those two remind me of tables "roster-groups" and "roster-items" - but "roster-groups" does not have any "groupname". As it seems, the published roster of owner "" (empty) is fetched: > storage_get(user->sm->st, "published-roster", "", NULL, &os) so creating that one would be the first step. To make it short: I still don't know what the code there is actually doing. Does someone have an SQL schema for those two tables? Or even an example how to use it? [1] http://codex.xiaoka.com/wiki/jabberd2:ideas [2] http://www.mail-archive.com/[email protected]/msg00991.html [3] http://mail.jabber.org/pipermail/jabberd/2004-March/001389.html [4] http://codex.xiaoka.com/svn/jabberd2/trunk/sm/mod_roster_publish.c -- Mit freundlichen Grüßen Christian Weiske -- To unsubscribe send a mail to [email protected]
