[zeromq-dev] 0MQ protocol stack

[Martin Pales]

On Wed, Apr 6, 2011 at 8:13 AM, Martin Sustrik <sustrik at 250bpm.com> wrote:

> The only thing changed atm is that the TCP connection initialisation.
> Instead of a simple message, a multipart message is sent where each part
> constitutes one property.
>
> However, I would not document that yet, as I am not at all confident in
> the model. In the first place we should understand why are the
> additional initialisation properties needed on top of TCP stack all.
>

I believe this is not only TCP related, right? All transports need to cover
the same functionality.
To achieve this, connection initialization could perform some sort of a
(transport independent) handshake to exchange required information and
perform checks, e.g socket types.

And since zmq works asynchronously, it would be nice to have a notification
system similar to the one in SCTP. For example, the "communication up"
notification could replace those artificial "READY" messages (used in the
guide). I can also imagine zmq-specific notifications like"hwm reached".

Just my thoughts as I am thinking about SCTP transport for zeromq. And since
zeromq transport already mimics some of SCTP features (message boundaries,
many to one style), it would be great also to have other features like the
aforementioned notifications and e.g. heartbeating also for other
transports.

Martin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20110407/1ebd3704/attachment.htm>