[phintjens]

Nice question. 0MQ has a wire protocol but it's minimalist, just doing framing. As we push 0MQ out into wider use we'll grow the protocol stack upwards. It'll take years. We do have a protocol specification project - http://rfc.zeromq.org/

We do intend to deliver IETF-quality specs that turn messaging patterns like pubsub into 1st class citizens of the Internet, so that arbitrary vendors can produce pieces that plug into this. But these specs will still be really simple.

I've always advocated a standard API for AMQP and proposed one (WireAPI) years ago, because this reduces vendor capture. Imagine if vendors designed arbitrary socket APIs... well some do, and it locks their users in.

So 0MQ is partly an API standardization project, partly an architecture project (to build a layer that seems to be missing from the stack), and partly a protocol specification project.

[setori88]

I wish you strength and that the community support you! It looks like a decent direction to move in. Your efforts at messaging pattern commodification on the Internet looks especially interesting, given your experience with restms. I hope this cracks it and makes life easy for all of us!

Crikey, it really doesn't get much more simple than that! http://rfc.zeromq.org/