W3C home > Mailing lists > Public > www-ws-arch@w3.org > May 2003

RE: MOM and reliable messaging article by Chris

From: Champion, Mike <Mike.Champion@SoftwareAG-USA.com>
Date: Mon, 12 May 2003 13:36:07 -0600
Message-ID: <9A4FC925410C024792B85198DF1E97E405A968C1@usmsg03.sagus.com>
To: www-ws-arch@w3.org

RFC 3080
http://www.ietf.org/rfc/rfc3080.txt

Is that the most recent, anyone?

> -----Original Message-----
> From: Cutler, Roger (RogerCutler) 
> [mailto:RogerCutler@chevrontexaco.com]
> Sent: Monday, May 12, 2003 3:32 PM
> To: Ugo Corda; jdart@tibco.com; www-ws-arch@w3.org
> Subject: RE: MOM and reliable messaging article by Chris
> 
> 
> 
> May I sincerely show my ignorance and ask -- WHAT THE HECK IS BEEP?
> 
> The term has come up several times and I guess I'm just 
> behind the eight
> ball.
> 
> -----Original Message-----
> From: Ugo Corda [mailto:UCorda@SeeBeyond.com] 
> Sent: Monday, May 12, 2003 1:53 PM
> To: jdart@tibco.com; www-ws-arch@w3.org
> Subject: RE: MOM and reliable messaging article by Chris
> 
> 
> 
> > This could be done without having an inter-process protocol in the
> > middle that isn't part of a vendor's MOM.
> 
> Yes, but in your scenario the intermediate process has to 
> know about all
> possible protocol-to-protocol combinations, while Chris' 
> approach would
> delegate to each individual MOM vendor the task of dealing with the
> conversion from proprietary protocol to HTTP (or BEEP).
> 
> Ugo
> 
> 
> 
Received on Monday, 12 May 2003 15:36:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:18 GMT