Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Personally, I prefer REST [uci.edu] to SOAP or XMLRPC. It's a whole lot simpler, does what you expect and doesn't involve SOAP::Lite.

    Of course it gives the Java/C++/C# folks fits because it doesn't neceessarily have any type information associated with it.

    -Dom

  • I would second the vote for REST. Much easier. However, I think the SOAP supporters have a legitimate case here. When you are looking for an interoperability protocol, broad industry support is one of the most important factors. It's kind of the point of the whole thing. If you have control over both ends and don't need to worry about interacting with Java and MS stuff, then you don't need to use web services at all.
  • But, hey, SOAP is more complex and has corporate backing so it *MUST* be better, right? The Java mentality strikes again. Dan, you're right about the Java mentality here ;-) I myself am a beginner to SOAP; when I was googling for articles on SOAP vs. XMLRPC, I found the link to that article. PFFFFFFFFFFFFFFFFTTTTTTTTTTTTTTTTTT. :-)) -- Sandeep http://sandeep.weblogs.us/