Re: REST, Conversations and Reliability

"Burdett, David" wrote:
> 
> Paul
> 
> I care greatly about technical quality, however I care more about success.

Me too! But a certain level of technical quality is a requirement for
success.

> What's needed is something that meets the business need that developers can
> then make work. It has to be good, it does not HAVE to be perfect.

Absolutely.

> So start with what already has traction, enhance it to meet the
> "requirements", and only change it when a "critical" requirement is not met.

The Web architecture of hypertext-based ecommerce has the most traction,
so we can start with that. Even in the world merely of machine to
machine applications using the interchange XML, the REST architecture is
already winning on the public Internet through the massive popularity of
RSS. The new Amazon API supports REST (explicitly, by choice) as a
superset of its SOAP functionality. Other large organizations (states,
fortune 500 companies) have contacted me to tell me they are adopting
REST. And SOAP implementors are starting to adopt the REST+SOAP model.

My argument with David Orchard is not about SOAP versus REST. It's about
whether www-ws-arch should proceed without a shared understanding the
Web's underlying architecture. If you read my critiques of his
correlation proposal, I did not tell him to take out the SOAP. I told
him to add the REST for reliability, discoverability, transparency,
interoperability and simplicity.
-- 
Come discuss XML and REST web services at:
  Open Source Conference: July 22-26, 2002, conferences.oreillynet.com
  Extreme Markup: Aug 4-9, 2002,  www.extrememarkup.com/extreme/

Received on Thursday, 18 July 2002 12:38:51 UTC