Beefy Boxes and Bandwidth Generously Provided by pair Networks RobOMonk
Problems? Is your data what you think it is?
 
PerlMonks  

Comment on

( #3333=superdoc: print w/ replies, xml ) Need Help??

Honey, that SOAP was ruined when you took it out of the RFC.

Perhaps our link-shotgunning anonymous monk will pepper you with REST links. If not, I’ll update with a few in a bit.

Update, few hours later…

Since SOAP is a protocol and REST is a set of architectural ideas/guides they’re not exactly swappable… still.

OpEd

I don’t have the space to explain all the problems [with SOAP] right now … but they boil down to massive interoperability problems. Good lord, you can’t even pass a number between languages reliably, much less arrays, or dates, or structures that can be null, or… It just doesn’t work. It’s not such a problem if you’re writing both the client and the server. But if you’re publishing a server for others to use? Forget it.

The deeper problem with SOAP is strong typing … [it] is a bad choice for loosely coupled distributed systems. The moment you need to change anything, the type signature changes and all the clients that were built to your earlier protocol spec break. And I don’t just mean major semantic changes break things, but cosmetic things like accepting a 64 bit int where you used to only accept 32 bit ints, or making a parameter optional. SOAP, in practice, is incredibly brittle. If you’re building a web service for the world to use, you need to make it flexible and loose and a bit sloppy. Strong typing is the wrong choice. Why SOAP sucks

Also: SOAP vs REST, tl;dr —> the answer is almost always REST.

Reading

Some relevant kits

No reviews, no endorsements

Routing grab bag

I wanted to code up a micro-example but ran out of time today. The router stuff is fun and micro-apps with Plack is too so I might revisit this one of these days with a new post.


In reply to Re: modern ways of doing web services by Your Mother
in thread modern ways of doing web services by Anonymous Monk

Title:
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!
  • 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
  • Outside of code tags, you may need to use entities for some characters:
            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?
    Username:
    Password:

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

    How do I use this? | Other CB clients
    Other Users?
    Others browsing the Monastery: (13)
    As of 2014-04-18 11:43 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?

      April first is:







      Results (466 votes), past polls