W3C home > Mailing lists > Public > www-ws-arch@w3.org > August 2002

RE: REST, Conversations and Reliability

From: Edwin Khodabakchian <edwink@collaxa.com>
Date: Wed, 7 Aug 2002 11:25:42 -0700
To: "'Ugo Corda'" <UCorda@SeeBeyond.com>, <www-ws-arch@w3.org>
Message-ID: <001a01c23e3f$d6a36750$670aa8c0@collaxa.net>


I think that your point is valid: "putting lipstick on the pig is not

But I believe that there is hope: look at how email servers evolved
thanks to SMTP.


> -----Original Message-----
> From: Ugo Corda [mailto:UCorda@SeeBeyond.com] 
> Sent: Wednesday, August 07, 2002 9:33 AM
> To: 'edwink@collaxa.com'; www-ws-arch@w3.org
> Subject: RE: REST, Conversations and Reliability
> >New technologies and standards
> >like XML, XML Schema, HTTP, URI could take existing messaging 
> >infrastructure that are priorietary and difficult to deploy 
> and manage 
> >across domains and make then ubiquitous.
> I would like that very much to happen myself, but I am not 
> convinced that it will, based on the current direction of things.
> The way people have been talking so far about messaging 
> infrastructure being combined with Web Services is at the 
> level of running SOAP on top of existing MOM systems like 
> MQSeries, MSMQ, etc. But these are all proprietary systems 
> (and using JMS as a common API does not change that). In 
> particular, when one of these systems is chosen, both 
> communication points must support the same system.
> I personally don't see how wrapping these messaging systems 
> in XML and SOAP can turn them into something non proprietary 
> and easy to deploy and manage. Maybe you had something else 
> in mind, which I would like to hear.
> Thank you,
> Ugo
Received on Wednesday, 7 August 2002 14:25:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:05:36 UTC