0MQ Requests for Comments

14/WMP - Worker-Manager Protocol - Raw
Worker-Manager Protocol is a generalization of request-reply pattern, allowing many workers talk to many managers (servers) with intermediate devices and custom load-balancing. This paper is a rather brief description of protocol, it lacks details and is not complete. I will do my best to finish it and to provide a reference implementation as soon as possible. (30 Jun 2011 08:45)

17/ZDCF - ZeroMQ Device Configuration File - Draft
The ZeroMQ Device Configuration File (ZDCF) specifies a standard language for configuring 0MQ devices. It provides information to configure a 0MQ context, and a set of 0MQ sockets. This specification aims to make it easier to build, share, and reuse 0MQ devices and build systems for device administration. (21 Mar 2012 07:04)

16/Collective Code Construction Contract (C4) - Draft
The Pedantic Code Construction Contract (PC3) is an evolution of the github.com Fork + Pull Model, aimed at providing an optimal collaboration model for commercial software projects. C4 is derived from the ZeroMQ contribution policy of early 2012. (18 Mar 2012 20:18)

12/CHP - Clustered Hashmap Protocol - Draft
The Clustered Hashmap Protocol (CHP) defines a cluster-wide key-value hashmap, and mechanisms for sharing this across a set of clients. CHP allows clients to work with subtrees of the hashmap, to update values, and to define ephemeral values. CHP originated from the Clone pattern defined in Chapter 5 of the Guide. (16 Apr 2011 12:18)

11/MTL - Message Transfer Layer - Draft
This document proposes a Message Transport Layer (MTL), a connection-oriented protocol that supports broker-based messaging. MTL connects a set of clients with a central message broker, allowing clients to issue commands to the broker, send messages to the broker, and receive messages back from the broker. (06 Apr 2011 10:44)

10/FLP - Freelance Protocol - Draft
The Freelance Protocol (FLP) defines brokerless reliable request-reply dialogs across an N-to-N network of clients and servers. It originated in Chapter 4 of the Guide. (13 Mar 2011 06:33)

9/TSP - Titanic Service Protocol - Draft
The Titanic Service Protocol (SP) defines a set of services, requests, and replies that implement the Titanic pattern for disconnected persistent messaging across a network of arbitrarily connected clients and workers. (08 Mar 2011 17:21)

8/MMI - Majordomo Management Interface - Draft
The Majordomo Management Interface (MMI) defines a namespace and set of management services that MDP brokers may provide. MMI is layered on top of the 7/MDP protocol. (05 Mar 2011 12:41)

6/PPP - Paranoid Pirate Protocol - Draft
The Paranoid Pirate Protocol (PPP) defines a reliable request-reply dialog between a client (or client) and a worker peer. PPP covers presence, heartbeating, and request-reply processing. It originated in Chapter 4 of the Guide. (28 Feb 2011 16:31)

5/ZDCF - ZeroMQ Device Configuration File - Draft
The ZeroMQ Device Configuration File (ZDCF) specifies a standard language for configuring 0MQ devices. It provides information to configure a 0MQ context, and a set of 0MQ sockets. This specification aims to make it easier to build, share, and reuse 0MQ devices and build systems for device administration. (09 Feb 2011 11:44)

4/ZPL - ZeroMQ Property Language - Draft
The ZeroMQ Property Language (ZPL) defines a minimalistic framing language for specifying property sets, expressed as a hierarchy of name-value property pairs. (24 Aug 2010 12:11)

13/ZMTP - ZeroMQ Message Transport Protocol - Stable
The ZeroMQ Message Transport Protocol (ZMTP) is a transport layer protocol for exchanging messages between two peers over a connected transport layer such as TCP. This document describes ZMTP/1.0 as implemented by the 0MQ/2.x generation of software. (30 Apr 2011 12:15)

7/MDP - Majordomo Protocol - Stable
The Majordomo Protocol (MDP) defines a reliable service-oriented request-reply dialog between a set of client applications, a broker and a set of worker applications. MDP covers presence, heartbeating, and service-oriented request-reply processing. It originated from the Majordomo pattern defined in Chapter 4 of the Guide. (28 Feb 2011 20:57)