Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
Extending my analogy above, SOAP is like buying manufactured cigarettes. No, you don't need to use them to cause damage, but easy availability increases the problem.

All of the other RPC mechanisms you discuss suffer from the same problems that I gave for SOAP. And in all of those cases the use of those on servers regularly leads to problems. They don't generally lead to horrible client issues though since the clients at least tend to be relatively solidly designed. (Compare IE with, say, Microsoft Word for security. There is no comparison. IE, for all of its mistakes, had to take it into account from day 1. Microsoft Word, as the routine macro viruses can attest, was not.) There is certainly nothing magic about SOAP that makes it better or worse than them.

But I single out SOAP because it is the protocol of choice for would-be buzzword-compliant people (a group who I have distrust and distaste for at best) who want to enable a wide variety of random clients to use a programatic interface to use over the Internet. It is particularly popular among people who want to do the kinds of things that firewall administrators (rightly) are inclined to audit and possibly block. It is even being marketed that way.

Therefore I believe that the density of scarily moronic things being done with SOAP is much higher than with the other RPC mechanisms that you mention. If people were being encouraged to open sloppily written Excel spreadsheets over the Internet with another RPC mechanism, I would be just as unhappy with it. But it isn't another RPC mechanism, it is SOAP which has that dubious honor, so it is SOAP I am speaking up about.

In reply to Re (tilly) 5: SOAP::Lite dispatch routine by tilly
in thread SOAP::Lite dispatch routine by gildir

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?

    What's my password?
    Create A New User
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others meditating upon the Monastery: (4)
    As of 2020-11-25 08:26 GMT
    Find Nodes?
      Voting Booth?

      No recent polls found