[Standards-JIG] MUC/pubsub multicasting using JEP-0033. Was: MUC traffic issues

Ulrich Staudinger us at activestocks.de
Mon Feb 20 21:01:45 UTC 2006


Ralph Meijer schrieb:

>On Mon, Feb 20, 2006 at 08:57:30PM +0100, Ulrich Staudinger wrote:
>  
>
>>    I don't see how this is different from an integrated MUC implementation
>>    using the current protocol. Replacing MUC's distribution scheme with
>>    pubsub's doesn't change anything. You'll still have as many messages
>>    coming into to the server (now as publishes) and the notifications
>>    coming out are also similar.
>>
>>
>>Actually, in the case of ejabberd where pubsub is built into the server you
>>have only one notification coming into the server and in the former scenario,
>>50 messages coming out.
>>    
>>
>
>So, as I said, this also holds if you integrate MUC into the server. No
>need to drag pubsub into this.
>
>  
>
Yeah, but what do you do when you have ten connection servers and you 
want users from all ten connection servers joining one particular room 
on one of the servers ?
That's where a pubsub like approach makes sense.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20060220/d79f0f95/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: us.vcf
Type: text/x-vcard
Size: 329 bytes
Desc: not available
URL: <http://mail.jabber.org/pipermail/standards/attachments/20060220/d79f0f95/attachment.vcf>


More information about the Standards mailing list