I am willing to bet anything (perverbaly) that this usage discrepency is
because most people consuming Amazon's WS are using PHP. In PHP <= 4
consuming a SOAP WS was especially complicated, having to either write
your own handler for a large and complex xml sub-language or use
something such as the nuSOAP library which is lacking in several key
areas. I believe this will change once PHP 5 takes a stronger foothold
since PHP 5 has it's own internal library for parsing SOAP which makes
consuming it much more natural.
My main gripe with REST is that most of the time, at least in my
experience, you have to write your own library to parse the extracted
information. There aren't a lot of developers doing this and for a large
project, say accessing Experians credit reporting products, there is a
significant amount of time that will need to be spent on just this
component. I have also noticed a lack of consistency among REST WS's,
some of which provide strings of information and others provide XML
with, obviously, their proprietary schema, which must also be learned
and parsed. As well, I'm a .NET developer so by nature I like things
fairly easy and quick to pick up and run with, hence SOAP is a natural
choice in that environment.
I agree though that both would be ideal and anything the church will
give me I am more than willing to consume. Perhaps if they give us a
REST WS then I will have to just create a .NET and a PHP library to
parse it and submit it to all of you.
Dave
Mac Newbold wrote:
Today at 7:57pm, Dave Wagner said:
Let me push my luck and suggest that SOAP be presented as the primary
means of exposing the churches content. XMLRPC and REST are just
annoying IMHO (REST especially).
As long as we're presenting suggestions, I suggest allowing both SOAP
and REST/XMLRPC. I find SOAP annoying, because I think it is too big
and bloated and complicated. People (especially developers) like
"simple" as long as it meets their needs, and only go complex when
necessary.
As an example, Amazon Web Services couldn't decide whether to choose
SOAP or REST, so they allowed them both. They were leaning to SOAP,
but were very suprised when they saw who used what. Over 80% of their
use (It may have been 90%, but I'm not sure, so I'll be conservative)
comes through REST, and only a small percentage through SOAP. [This
was presented by Jeff Barr, their Web Services Evangelist, on
9/29/2005 at a UPHPU meeting, among other places and times.]
Anyway, if we're throwing pennies around, there are mine.
Mac
--
Mac Newbold MNE - Mac Newbold Enterprises, LLC
[EMAIL PROTECTED] http://www.macnewbold.com/
_______________________________________________
Ldsoss mailing list
[email protected]
http://lists.ldsoss.org/mailman/listinfo/ldsoss
_______________________________________________
Ldsoss mailing list
[email protected]
http://lists.ldsoss.org/mailman/listinfo/ldsoss
