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
easy to pin down too.
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
SOAP vs. REST (Score:3, Insightful)
The key issue is this: there are some operations that are safe, and always return the same conceptual result: http://www.google.com/search?q=perl, http://www.news.com/, http://search.cpan.org/search?dist=perl. The way the web was designed, these resources are identified by their URLs, and should be retrievable with GET requests. They can then be referenced anywhere you can place a URL -- web pages, XPath expressions, XSLT stylesheets, RDF assertions, XLinks, etc.
The issue behind putting resources such as this behind a POST request (using SOAP, XML-RPC or any other technique you care to use) is that such uses of HTTP POST have the nasty effect of hiding information and inhibiting it's use elsewhere on the web.
OTOH, the SOAP advocates color this debate as simply a few academics crying for intellectual purity, aesthetic beauty and spilled milk because the other side "has won".
Reply to This