[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jabber-jdev
Subject:    RE: [jdev] Rooms and user attributes
From:       Steve Smith <ssmith () vislab ! usyd ! edu ! au>
Date:       2005-06-17 0:07:55
Message-ID: 1118966875.1083.8.camel () moth ! vislab ! usyd ! edu ! au
[Download RAW message or body]

> Jabber (MUC) rooms do not store user attributes other than the status
> (admin, visitor, participant...) and other chat related bits. There are
> no custom user properties in rooms. Anyway, I guess you want to manage
> user attributes across rooms and not per room. So, that the user rating
> from one room is available in another room. This means, that it is not
> sufficient that the room stores user attributes. This is definitely not
> available now. It must be programmed.

One (possible) hack to store extra room information is to have a special
user on the server with predefined name who maintains a pubsub node with
this information.  So if you have a MUC room
'lounge@conference.example.com' you create a user
'moderator@example.com' who owns a pubsub node
'<userroot>/muc/lounge/extra' that contains the information.  Clients
that understand the convention can just subscribe to that node.

The advantage to this is it can be done without server modifications
(this would work out of the box with ejabberd).  But it feels a bit of a
hack.  I'm planning on using this for some multicast support for MUCs,
so I'd be interested in hearing comments on this.

Cheers,
Steve

_______________________________________________
jdev mailing list
jdev@jabber.org
http://mail.jabber.org/mailman/listinfo/jdev
[prev in list] [next in list] [prev in thread] [next in thread]