over here, https://gist.github.com/3243702, i proposed extending the text protocol by supporting updating a timer with multiple values at once (to help statsd clients that do a bit of batching for efficiency). this makes the update string a bit expensive to parse (especially because you have to get to the end of a potentially long string to even know what kind of update you have).
so here are some thoughts on a different way to encode the statsd update.
if we chose one of these, so we could call this protocol version "2" in our zeromq input (e.g. zmq message payload would be "2;").