[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: What does SOAP really add?

• To: "Adam Turoff" <ziggy@p...>,"Dave Winer" <dave@u...>
• Subject: RE: What does SOAP really add?
• From: "Joshua Allen" <joshuaa@m...>
• Date: Mon, 22 Apr 2002 20:19:32 -0700
• Cc: "Edd Dumbill" <edd@u...>,<xml-dev@l...>
• Thread-index: AcHqcFB3E/I0gV8wTNqdEMjFjQ2X1QAA/DQA
• Thread-topic: What does SOAP really add?

> I shudder to think what will happen when someone tries to publish
> a SOAP API with a more complex schema.  We won't get interoperability
> by waving the magic WSDL pixie dust, and we'd be significantly
> better off with some kind of task-specific XML document structure
> with REST.

This FUD is getting more strident and ridiculous by the week.  Not only
does WSDL+SOAP work, hundreds of companies are using it in
mission-critical systems.  I would be shocked if more than half of the
fortune 500 didn't have production SOAP-enabled systems in some part of
their enterprise.  I can understand if you are upset that
loosely-coupled XML messaging EAI is the dominant mode of interop for
businesses.  But all the thinking and shuddering (or was it fear and
trembling and doubt) in the world doesn't change the simple *fact* that
this stuff works, and lots of people buy the value proposition.

I am certainly not opposed to debate over the merits of REST vs. RPC
architecture for various architectures, but saying "it won't work" is a
great way to start off with so little credibility as to be practically
incredible.

• Follow-Ups:
  • Re: What does SOAP really add?
    • From: Adam Turoff <ziggy@p...>

• Prev by Date: Re: What does SOAP really add?
• Next by Date: RE: What does SOAP really add?
• Previous by thread: RE: What does SOAP really add?
• Next by thread: Re: What does SOAP really add?
• Index(es):
  • Date
  • Thread