Developing custom clients speaking custom protocols to custom server-side Unix daemons is something I have come to believe is a very wrong approach for the first iteration of a solution, especially given how ???easy??? it is to hack something together on top of a REST API. Twitter, for example, has only recently switched to a classic always-connected client-server configuration (they call it ???real