[jdev] A case for private XML storage in MUC rooms

cascardo at minaslivre.org cascardo at minaslivre.org
Wed Jul 13 20:56:34 CDT 2005


I like your idea because I'm particularly interested in that for an
application of mine. However, I like the pubsub approach and I think
we could discuss about it. I would be very interested in helping you
implement it.

I will try to answer your points about pubsub below.

On Wed, Jul 13, 2005 at 02:51:31PM +1000, Steve Smith wrote:
> Hi,
> I'm currently looking at methods of associating multicast addresses and
> other metadata with MUC rooms, and I've come to the conclusion that
> there is a case for per-room private XML storage, similar to
> JEP-0049 ...
> How it would work:
> The semantics would be virtually identical to the JEP-0049 with the
> following exceptions:


>         Use pubsub: A method of specifying the location of the pubsub
>         node would still be required, and then additional
>         access-restrictions would need to be implemented on the pubsub
>         node itself.  In particular the access-restrictions would need
>         to be updated to match the changing membership of the room.

Well-known node locations are possible and disco items is there for
discovering it too. For the access restrictions, a particular
implementation of muc could publish the node automatically and
updating access restrictions every time a user is registered or
unregistered (or join/leave the room). Being on the same host and if
the whitelist of subscribers is not persistent, there should be not
much of an overhead for this updating.

Use Jabber!
cascardo at jabber.org

>         More: There are certainly other angles I haven't considered,
>         comments are more than welcome.
> Other uses:
> There are plenty of cases where a room owner (and moderator?) may wish
> to attach useful information to a room in a manner that doesn't require
> them to be connected to the room: a longer MOTD than is suitable for a
> subject line, room specific bookmarks (using JEP-0048), etc.
> I'm going to create an implementation of this in ejabberd if anyone is
> interested in playing with it.
> Cheers,
> Steve
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mail.jabber.org/mailman/listinfo/jdev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://mail.jabber.org/pipermail/jdev/attachments/20050713/223c14e9/attachment-0002.pgp>

More information about the JDev mailing list