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.
>
> ----- Original Message -----
> From: "Bill Abbas" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, June 07, 2001 5:27 PM
> Subject: [JDEV] MQSeries and Jabber
>
> >
> > This is probably a bit off-topic, but ...
> >
> > I'm beginning an evaluation of IBM's MQSeries messaging
> > system and am wondering how it overlaps or complements the
> > Jabber protocol.
> >
> > Obviously, they're both messaging systems, although MQ
> > seems to be more programmatic, while Jabber is more
> > concerned with text messages. Has anyone looked into, say,
> > implementing the MQ API as a Jabber transport, or using MQ
> > as an underlying transport for Jabber XML messages?
> >
> > =Bill
> > _______________________________________________
> > jdev mailing list
> > [EMAIL PROTECTED]
> > http://mailman.jabber.org/listinfo/jdev
>
> _______________________________________________
> jdev mailing list
> [EMAIL PROTECTED]
> http://mailman.jabber.org/listinfo/jdev
--
[EMAIL PROTECTED] http://sdw.st
Stephen D. Williams
43392 Wayside Cir,Ashburn,VA 20147-4622 703-724-0118W 703-995-0407Fax
Dec2000
_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
