David Sutton wrote: > In view of the recent discussion, support for browse has been dropped in > MU-Conference cvs code, ready for when the disco protocol goes draft.
David, I think this decision is very unfortunate, if I may speak for the client developers. I guess many have built some browse UI for use with jabber:iq:conference that is very practical to reuse when testing out the MUC protocol. I agree that support for jabber:iq:browse should only be considered temporary, and later phased out and replaced by disco. But meanwhile, keep some sort of support for browse, at least as a help in assisting client developers testing MUC. > made it more complicated to retrieve the data necessary. What I may do > is make browse an optional extra which can be enabled or disabled at the > service admins choice. If I do this, then the SHA hash idea (for > representing a users true jid, not roster entry) may also be an option. > I really perceive this being of use in certain situations, even if > others may not yet. Sounds like a reasonable compromise to me. Hope this post is not completely out of sync... Best Wishes, Mats _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
