I used WAMP extensively in a desktop app a few years ago. Ironically, we only used it only for IPC, not communication to a remote web service. Why? * It provi

I used WAMP extensively in a desktop app a few years ago. Ironically, we only used it only for IPC, not communication to a remote web service. Why? * It provided "routed RPC", which made IPC between many heterogeneous desktop apps easy (a service, a tray icon process, main UI process, a couple of others etc). * It supports PubSub as well as RPC. * It works over TCP, rather than e.g. unix domain sockets, which means it's portable and interoperable (I didn't use the WebSocket transport because the library I used supported raw TCP, but you can mix and match). We bound to loopback. * Because it was built for JavaScript, it was all dynamic, which meant no code generation. The only viable alternatives, and their dependencies, were going to be a pita to build and integrate in to our build system on all 3 major platforms and were going to result in terrible code. * The protocol is JSON which made debugging issues very easy.