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.
  • SOAP vs. REST (Score:3, Insightful)

    by ziggy (25) on 2002.04.26 15:28 (#7625) Journal
    Java found a place without displacing any other languages. Maybe REST can find a place without having to displace SOAP in the process.
    According to the REST folks, it's not an open playing field where the two could live in harmony. What's at stake is nothing less than the web as we know it. So while Java, Perl, C++ and C# can live in harmony in an open system we call the IT sector, SOAP and REST can't live in harmony in the closed system we call the Web.

    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".