techSanctuary

I've seen arguments for both. REST is smaller over the wire, while SOAP allows complex types. Obviously each has its place. But when we are talking about web services, isn't standardization key? I'm currently working on a project to build a search abstraction layer. Having to support both protocols is an annoyance. Add to REST and SOAP the possibility of also having to support XML-RPC and things get silly. Personally, I don't mind using a few extra resources for SOAP if it means using one protocol. Computing resources are cheap these days.