Lists Home |
Date Index |
- From: Dave Winer <email@example.com>
- To: "Simon St.Laurent" <firstname.lastname@example.org>, email@example.com
- Date: Fri, 04 Aug 2000 09:52:44 -0700
What does the size of a project have to do with it?
How do you measure the size of a project?
Further, the complexities (or lack of) in any protocol are completely hidden
behind APIs. I do SOAP and XML-RPC with equal ease. The only issue is what
they interoperate with. (And perhaps performance, but I doubt if there's any
difference between the two encodings.)
----- Original Message -----
From: "Simon St.Laurent" <firstname.lastname@example.org>
Sent: Friday, August 04, 2000 9:22 AM
Subject: Re: XML-RPC or SOAP
> At 09:03 AM 8/4/00 -0700, Dave Winer wrote:
> >XML-RPC is alive and well.
> >SOAP is coming along, but there aren't many interoperable
> >and none of them implement all the possibilities. So interoperability is
> >still a challenge in SOAP-space, where it's trivial in XML-RPC, and done,
> >and demonstrated.
> >So my advice is this, if XML-RPC does what you need to do, use it.
> For once, I'll agree with Dave 100%.
> SOAP may be more 'advanced', but XML-RPC is very convenient and easy to
> learn. For small projects, and maybe even for some relatively simple big
> projects, XML-RPC makes a lot of sense.
> (I like to say that XML-RPC gives you enough rope to hang yourself, but
> SOAP gives you enough rope to hang yourself and a lot of other people too.
> Rope is, of course, useful for other things as well!)
> Simon St.Laurent
> XML Elements of Style / XML: A Primer, 2nd Ed.
> http://www.simonstl.com - XML essays and books