8/MMI - Majordomo Management Interface

+ Table of Contents

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.

Name: rfc.zeromq.org/spec:8/MMI
Editor: Pieter Hintjens <moc.xitami|hp#moc.xitami|hp>
Contributors: none

License

This Specification is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version.

This Specification is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program; if not, see <http://www.gnu.org/licenses>.

Change Process

This Specification is a free and open standard[2] and is governed by the Digital Standards Organization's Consensus-Oriented Specification System (COSS)[3].

Language

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119[1].

Goals

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.

The goals of MMI are to:

Define a namespace for management services provided by a MDP broker to MDP client applications.
Define a default set of management services that MMI-compatible brokers SHOULD implement.

Architecture

Namespace

An MMI broker implementation MUST handle all services that start with "mmi." internally. It MUST disconnect any workers that attempt to register servics in this namespace.

Default services

An MMI broker implementation MUST implement these services:

mmi.service - accepts a request containing a service name, responds with "200" (Found) if there is at least one worker registered for the service, or "404" (Not found) if there are no workers registered for the service.

Any unimplemented services in the "mmi." namespace MUST result in a reply "501" (Not implemented).

Reference Implementations

The C99 Majordomo examples from Chapter 4 of the Guide[4] act as the prime reference implementation for MMI. Translations of the examples into other languages may be available.

References

Bibliography

1. "Key words for use in RFCs to Indicate Requirement Levels" - ietf.org

2. "Definition of a Free and Open Standard" - digistan.org

3. "Consensus Oriented Specification System" - digistan.org

4. "ØMQ - The Guide" - zeromq.org

Edit | Tags | Source | Print

Use the zeromq-dev list to discuss this specification.

Note on use of the GPL: we use this license to cover the specification text itself, not implementations. You can license your own code under any license you wish. If you make derived versions of this specification, you must share them under the GPL. The goal of this is to prevent private extensions of our specifications.

This specification has at least one implementation (draft).

Set the state of this specification