Agreed. I tried to use msgpack and ran into all sorts of weird recursion issues (basically, it threw up on even the simplest objects). I ended up just using gzip and it works great.
I think if you control both ends of the interaction, lz4 or snappy may be interesting to use. But for most things, I do think gzip is better supported (especially http).
I'm storing data in redis via node.js. It was taking forever to xfer it over the wire. I compressed it with gzip using node's built in support. Problem solved.
I tried snappy, but found it was a) slower and b) bigger. Not having to have yet another dependency was also a plus for gzip.
Which language's binding did you use? MessagePack is a protocol, not an implementation. Anyway, if gzipping worked great for you, that sounds like the way to go =)
Comments
Agreed. I tried to use msgpack and ran into all sorts of weird recursion issues (basically, it threw up on even the simplest objects). I ended up just using gzip and it works great.
I think if you control both ends of the interaction, lz4 or snappy may be interesting to use. But for most things, I do think gzip is better supported (especially http).
I'm storing data in redis via node.js. It was taking forever to xfer it over the wire. I compressed it with gzip using node's built in support. Problem solved.
I tried snappy, but found it was a) slower and b) bigger. Not having to have yet another dependency was also a plus for gzip.
Which language's binding did you use? MessagePack is a protocol, not an implementation. Anyway, if gzipping worked great for you, that sounds like the way to go =)