SOAP is dirty!

Contrary to popular belief, SOAP is dirty! When folks talk about web services they immediately think SOAP, which is unfortunate. When I think of a web service I think of system either a web site, a service running in your companies intranet, even a service running on the same machine, that I can send simple messages to and receive responses. The key is SIMPLE messages.

Yes, that’s a rather loose definition. Mail servers probably fall into that definition, but to me that’s a web service. Well not very webby but a service nonetheless. So if SOAP is dirty what else can you use to create web services? Well there’s the venerable XML-RPC which is truly simple unlike SOAP. Most people don’t use XML-RPC because it doesn’t support “objects”, but then again those are overrated too. Seriously folks, you send a message you get back a structure. You really don’t need more than a hash or an array.

Other reasons folks don’t like XML-RPC are that it lacks support for long data types (only supports integers), UTF-8 encoding (makes it hard to use for internationalization), and doesn’t have the concept of null. Those are all valid reasons, but a lot of times you don’t need that stuff in which case it’s still better to use XML-RPC rather than SOAP. The ease of development and ease of use from an api users point of view out weighs a lot of those things. XML-RPC is also trivial to understand. The specification is easy to digest: Compare that to the monstrosity of the SOAP spec. There still quite a few application that use XML-RPC as an API:, func, Red Hat Network, and flickr.

If the limitations of XML-RPC truly are deal breakers for you, you’re probably wondering “I guess I’ll need to use SOAP!” Well, aside from needing soap to stay clean, you can actually be SOAP free in your web services and still use longs, nulls, etc. How? Use REST.

There are two ways to implement REST services. There’s the purist way which uses the verbs of the HTTP protocol such as PUT, DELETE, POST, etc. The other more common way is to simply use the GET and POST. You supply your parameters on the URL including the method to be called and get back an XML response. A downside to REST is that the XML response is defined by the web service implementor, unlike XML-RPC or SOAP which have a defined structure. Nonetheless, REST has become very popular among web sites such as,, and

REST and XML-RPC are not the only alternatives to SOAP, JSON is another. JSON is commonly done as a REST web service with the exception that the response is in JSON format. Most folks assume JSON is for use with JavaScript and web applications only, but that is not true. The thing I like most about JSON + REST is I get the ease of calling by a simple URL and get a well formatted easy to read response that supports nulls, UTF-8, and longs. You get none of the scum from SOAP, none of the limitations of XML-RPC, and a well understood format unlike the typical REST response.

Ok the best way to “see” this is by looking at some code. Let’s look at XML-RPC first. Let’s assume we are calling the “smugmug.images.get” method at Using an XML-RPC library for your language (java, python, perl).

client = ServerProxy("")
session = client.loginWithPassword("uname", "pass")
imgdata = client.smugmug.images.get(session, image_id)
print imgdata['id']

It’s that simple. The library did the parsing for me. imgdata will most likely be a hash. The library sent over something like this:

<?xml version="1.0"?>

The server responds with something like this:

<?xml version="1.0"?>

Pretty easy to read isn’t it? But as you saw in the code you didn’t have to know how to read it.

Let’s try the same thing with REST. There are no frameworks that handle REST directly as it’s just a simple HTTP GET or POST and an XML document response.
url = ""
call = url + "?method=smugmug.images.get&session=AXE0123&id=40"
response = urllib.urlopen(call).read()
# parse response XML into a dictionary
imgdata = parse(response)

In most cases you’ll probably have to write your own framework which isn’t really that hard, I did it. What gets sent out is a simple HTTP GET request to What you get back is an XML document which you will need to parse.

<?xml version="1.0" encoding="utf-8" ?>
<rsp stat="ok">
  <Image id="17833"/>
  <Image id="17832"/>

Yes, it’s XML but so far it’s not too bad is it? You’re probably itching to see what JSON and SOAP can do huh? Well, heeeeere’s JSON! (that’s a Johnny Carson reference for you youngins).

url = ""
call = url + "?method=smugmug.images.get&session=AXE0123&id=40"
response = urllib.urlopen(call).read()
# use builtin python library simplejson to read
imgdata = simplejson.loads(response)

The nice part about this is I don’t have to parse the response because libraries like simplejson do that for me. And I can easily make the calling code generic as I did in Again, the request is nothing more than a simple HTTP GET. The response is a nice JSON object.


As you can see it is very easy to read and no nasty XML to deal with either. Best part is you could use this in an AJAX web ui with no need to create more than one API.
There you have it, nice alternatives for creating web services without using SOAP.

Oh you want to see the SOAP version of the above? hrm. smugmug was wise not to create a SOAP version of the API, but here is what it would probably look like. I’m warning you, you don’t want to see it. Ok here goes.

  import org.apache.axis.client.Call;
  import org.apache.axis.client.Service;
  import javax.xml.namespace.QName;

  public class TestClient {
    public static void main(String [] args) {
      try {
        String endpoint =

        Service service = new Service();
        Call call = (Call) service.createCall();

        call.setTargetEndpointAddress( new );
        call.setOperationName(new QName("", GetImagesFromSmugmug"));

        List<Integer> ret = (List<Integer>) call.invoke( new Object[] { "AXE0123", new Integer(40) } );

        System.out.println("Sent 'Hello!', got '" + ret.toString() + "'");
      } catch (Exception e) {

Yes, I know it’s Java and not python, but that’s another problem with SOAP. The better libraries are written for Java not python, perl, etc.

What would the SOAP request look like you ask? Probably like this:


Followed by a nasty response:

         xsi:type="xsd:int" mustUnderstand="1">

Seriously folks, it is truly possible to create web services and software as a service WITHOUT resorting to the evil that SOAP is. So the next time you plan on developing a web services api for your application consider XML-RPC, REST, and JSON.


I don’t like to forward all the spammy email’s I get from friends, but I don’t mind sharing them here 🙂 I got this one this morning and laughed my butt off.

The Centre for Disease Control has issued a medical alert about a highly contagious, potentially dangerous virus that is transmitted orally, by hand, and even electronically. This virus is called Weary Overload Recreational Killer (WORK). If you receive WORK from your boss, any of your colleagues or anyone else via any means whatsoever – DO NOT TOUCH IT. This virus will wipe out your private life completely. If you should come into contact with WORK you should immediately leave the premises. Take two good friends to the nearest grocery store and purchase one or both of the antidotes – Work Isolating Neutralizer Extract (WINE) and Bothersome Employer Elimination Rebooter (BEER). Take the antidote repeatedly until WORK has been completely eliminated from your system. You should immediately forward this medical alert to five friends. If you do not have five friends, you have already been infected and WORK is controlling your life.

Weekend summary

This weekend we drove to Maryland, yes again. While in Maryland I lost my only set of keys for my car. It’s yet another sign that it’s time for a new car. But getting a set of new keys is $170 compared to a new car 🙂 So we put off the inevitable a little longer.

But that was the only bad news from this weekend. The reason we made the trip at all was to see Frank, my father-in-law, through his surgery for prostate cancer. He had the surgery done at NIH by a surgeon formerly from John Hopkins. We felt he was in good hands with that combination as opposed to his crappy insurance: Kaiser Permanente.

Frank is doing well after surgery. He had his entire family present to make sure he was ok. Hopefully he’ll be going home tomorrow.

DHL are freakin’ IDIOTS!

I order a package with one day shipping from to be delivered today. Amazon chose DHL to ship my package, which was a mistake.

I checked the tracking this morning and it said out for delivery. I didn’t get a chance to check it again until I got home. I called customer service and they confirmed my address and stated the driver couldn’t find it. COULD NOT FIND IT! Apparently they haven’t heard of Google Maps or anything. The USPS has no problem. Neither does UPS. Even FedEx can find my house. Hell, using Google Maps you can see the playset in our backyard, the boulder, even the oil stain my car left in the driveway. With all this technology this so called shipping company couldn’t find my house!


I am just really pissed off at this incompetence. How can you be a damn shipping company and not be able to find the places you deliver to. That’s the last time I use DHL for any of my personal shipping, and if DHL is Amazon’s choice for their Prime service I will not renew next year.