[JDEV] MQSeries and Jabber

[Rahul Dave]

I thought as much about presence..

About messages, what is the current thinking on multicasting at the server?
For example, in the Net::Jabber example for sending headlines, the perl
script has to construct and send messages for all the subscribers. This is
a serial process; on a multi-server platform this could be parallelized..?

Rahul
I got this from you:
> 
> Presence is sent to the server from the client only once, then the server
> takes over from there. 
> 
> On Thu, 7 Jun 2001, Rahul Dave wrote:
> 
> > I got this from you:
> > > 
> > > Al Sutton wrote:
> > > > 
> > > > One of the big differences I can see is that MQ is a publish/subscribe
> > > > architecture (i.e. one person publishes a message, others subscribe to the
> > > > channel and all subscribers receive that message), where as Jabber is
> > > > designed with point-to-point communication being the main concern.
> > > 
> > > But you forget that presence itself is fundamentally a publish/subscribe
> > > system.  It's secondary use is to setup point-to-point message routing.
> > > 
> > > Both interfaces can and will be generalized as communication models.
> > > 
> > > sdw
> > > 
> > > > Al.
> > > > 
> > > > P.S. I'm aware of the efforts going into conferencing, but the basis of
> > > > Jabber seems to have been point-to-point.
> > 
> > Currently, if one wants to multicast a message in jabber, dosent the client
> > have to pull over the roster and send messages one by one to the server, which
> > routes them?
> > 
> > Does presence work in the same way? or can the server send the presence
> > update to interested parties?
> > 
> > Rahul
> > _______________________________________________
> > jdev mailing list
> > jdev at jabber.org
> > http://mailman.jabber.org/listinfo/jdev
> > 
> 
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
>