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
