I've thought about this a few times (fleetingling since I don't know all that much about MQ systems) and it seems to me that that would be a useful thing to add to Jabber (especially when heading the JAM route). However, since (I believe) all the major MQ software (SonicMQ, IBM MQ Series, etc) are JMS compliant, you should be able to write things in compliance with JMS and the MQ software should interoperate, yes?
I like this idea....
Thoughts?
> -----Original Message-----
> From: Michael Bauer [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 07, 2001 12:04 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: [JDEV] MQSeries and Jabber
>
>
>
> Hi, Bill. IANAE (I am not an engineer) but I know that we've
> discussed this
> kind of thing specifically at Jabber.com. Of course, in
> parallel, the JAM
> inititive has already been investigating the usefulness of
> message queueing,
> delivery guarantees, and transaction processing that MQ
> provides, as far as
> I understand.
>
> -----Original Message-----
> From: Bill Abbas [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 07, 2001 10:27 AM
> To: [EMAIL PROTECTED]
> 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
>
