• From: Francis Norton <francis@r...>
• To: Michael Brennan <Michael_Brennan@a...>
• Date: Tue, 21 Aug 2001 09:10:29 +0100

Michael Brennan wrote:
> 
> 
> That's what's driving WSDL. As web services mature, very few programmers
> using web services tools will be dealing with XML APIs (unless they want
> to).
> 
I wrote a literal-xml-only soap library for an early implementation, and
when I downloaded the MS SOAP kit I couldn't believe all the WSDL cruft
that was cluttering it up.

Having now used WSDL in .NET to generate complete sync and async proxy
client classes, and fairly useful abstract server classes, I now realise
it's not cruft, it's the key. As David Platt says, it's type library
definitions for the internet. And once you've got those, you're really
cooking. 

Francis.

• Follow-Ups:
  • Re: "Uh, what do I need this for" (was RE: XML.COM: How I Learne d toLove daBomb)
    • From: Edd Dumbill <edd@u...>

• References:
  • RE: "Uh, what do I need this for" (was RE: XML.COM: How I Learne d to Love daBomb)
    • From: Michael Brennan <Michael_Brennan@a...>

• Prev by Date: Why different languages codes 639-2/T and 639-2/B
• Next by Date: Re: Namespaces, schemas, Simon's filters.
• Previous by thread: RE: "Uh, what do I need this for" (was RE: XML.COM: How I Learne d to Love daBomb)
• Next by thread: Re: "Uh, what do I need this for" (was RE: XML.COM: How I Learne d toLove daBomb)
• Index(es):
  • Date
  • Thread