[zeromq-dev] 0MQ protocol stack

[Pieter Hintjens]

Martin,

Imagine there's a project that wants to use the 0MQ TCP protocol for
something, but implement its own stacks. We know that there aren't
proper specifications for the 0MQ stack, but my questions are rather:
what should we call this protocol, and how should the stack be broken
up. E.g. do we want a spec for the framing, and another for
handshaking over TCP, and another for PGM, and another for inproc?

If we can decide on the shape of the stack, and names for the pieces,
it becomes a lot easier to fill in the blanks.

Given that the protocol is going to change for 3.0 I think it's an
opportunity to spec it out *before* implementing it, rather than
making the same mistake as before. This would give people a chance to
review and improve, rather than argue over a defacto implementation.

I'm happy to work on writing specs, but only within a framework (i.e.
that stack and the names for pieces) that's been agreed upon.

-Pieter