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.
  • > like pointlessly wrapping SMTP in XML-RPC.

    This largely describes "web services" in general.

    Well, I've seen three kinds: (1) toy examples, (2) wrapping of propietary protocols into XML (they will still be closed and proprietary, mind, as long as the vocabularies and protocols are not public), and then these (3) pointless rewrappings of existing protocols/frameworks.

    In (2) and (3) the only measurable effect has been manifold increase in bandwidth, and the need to have an XML parser everywhere. Not to mention that the whole RPC request-reply paradigm is ill-suited for many networking environments. Oh, joy.

    If I've hurt someones feelings who think web services are the greatest thing since sliced bread, I'm sorry. I just don't see much net benefit.
    • I just don't see much net benefit.

      Is that a pun :)

    • If I've hurt someones feelings who think web services are the greatest thing since sliced bread, I'm sorry. I just don't see much net benefit.

      No, that pretty much nails it. Web Services are a vast conspiracy of deep-pocketed vendors and tagheads to make themselves relevant.

      There are a few benefits to Web Services, like the reinvention of IDL and "baked in platform neutrality", but there were better ways to get those benefits than XML-RPC, SOAP, WSDL, and RWSA(*) provide. For example, wrapping a pr