imported>SchlurcherBot: Bot: http → https

2025-06-23T20:34:58Z

Bot: http → https

New page

{{Short description|Computer network protocol}}
{{primary sources|date=May 2018}}
{{Use dmy dates|date=September 2014}}
{{Infobox networking protocol
| logo =
| logo alt =
| image =
| image alt =
| caption =
| abbreviation = AMQP
| purpose = [[Message-oriented middleware]]
| developer = AMQP working group ([[OASIS (organization)|OASIS]])
| date = {{Start date and age|2003| | }}
| based on =
| influenced =
| osilayer =
| ports =
| rfcs =
|title=Advanced Message Queuing Protocol}}
The '''Advanced Message Queuing Protocol''' ('''AMQP''') is an [[open standard]] [[application layer]] protocol for [[message-oriented middleware]]. The defining features of AMQP are message orientation, queuing, [[routing]] (including [[Point-to-point (telecommunications)|point-to-point]] and [[Publish–subscribe|publish-and-subscribe]]), reliability and security.<ref name="acmqueue">{{cite journal
| author = O'Hara, J.
| year = 2007
| title = Toward a commodity enterprise middleware
| journal = ACM Queue
| pages = 48–55
| doi = 10.1145/1255421.1255424
| ref = refohara
| volume = 5
| issue = 4
| doi-access = free
}}
</ref>

AMQP mandates the behavior of the messaging provider and client to the extent that implementations from different vendors are [[interoperable]], in the same way as [[SMTP]], [[HTTP]], [[FTP]], etc. have created interoperable systems. Previous standardizations of [[middleware]] have happened at the API level (e.g. [[Java Message Service|JMS]]) and were focused on standardizing programmer interaction with different middleware implementations, rather than on providing interoperability between multiple implementations.<ref>{{cite journal
| author = Vinoski, S.
| year = 2006
| title = Advanced Message Queuing Protocol
| journal = IEEE Internet Computing
| pages = 87–89
| doi = 10.1109/MIC.2006.116
| url = https://steve.vinoski.net/pdf/IEEE-Advanced_Message_Queuing_Protocol.pdf
| volume = 10
| issue = 6
| s2cid = 14211884
}}</ref> Unlike JMS, which defines an API and a set of behaviors that a messaging implementation must provide, AMQP is a [[Wire protocol|wire-level protocol]]. A wire-level protocol is a description of the format of the data that is sent across the network as a [[byte stream|stream]] of [[octet (computing)|byte]]s. Consequently, any tool that can create and interpret messages that conform to this data format can interoperate with any other compliant tool irrespective of implementation language.

== Overview ==
AMQP is a [[Binary protocol|binary]] application layer protocol, designed to efficiently support a wide variety of messaging applications and communication patterns. It provides flow controlled,<ref>{{cite web|title=OASIS AMQP version 1.0, sections 2.6.7-2.6.8|url=https://docs.oasis-open.org/amqp/core/v1.0/amqp-core-transport-v1.0.html#doc-flow-control|publisher=OASIS AMQP Technical Committee|access-date=18 June 2012}}</ref> message-oriented communication with message-delivery guarantees such as ''at-most-once'' (where each message is delivered once or never), ''at-least-once'' (where each message is certain to be delivered, but may do so multiple times) and ''exactly-once'' (where the message will always certainly arrive and do so only once),<ref>{{cite web|title=OASIS AMQP version 1.0, sections 2.6.12-2.6.13|url=https://docs.oasis-open.org/amqp/core/v1.0/amqp-core-transport-v1.0.html#doc-idp489648|publisher=OASIS AMQP Technical Committee|access-date=18 June 2012}}</ref> and authentication and/or encryption based on [[Simple Authentication and Security Layer|SASL]] and/or [[Transport Layer Security|TLS]].<ref>{{cite web|title=OASIS AMQP version 1.0, section 5.1|url=https://docs.oasis-open.org/amqp/core/v1.0/amqp-core-security-v1.0.html#section-security-layers|publisher=OASIS AMQP Technical Committee|access-date=18 June 2012}}</ref> It assumes an underlying reliable transport layer protocol such as [[Transmission Control Protocol]] (TCP).<ref>{{cite web|title=OASIS AMQP version 1.0, section 2.1|url=https://docs.oasis-open.org/amqp/core/v1.0/amqp-core-transport-v1.0.html#section-transport|publisher=OASIS AMQP Technical Committee|access-date=18 June 2012}}</ref>

The AMQP specification is defined in several layers: (i) a type system, (ii) a symmetric, asynchronous protocol for the transfer of messages from one process to another, (iii) a standard, extensible message format and (iv) a set of standardised but extensible 'messaging capabilities.'

== History ==
AMQP was originated in 2003 by John O'Hara at [[JPMorgan Chase]] in [[London]].<ref name="acmqueue" /><ref>{{cite web|title=Background to the AMQ Project, Authors|url=https://github.com/imatix/openamq/blob/master/website/doc_background.txt|last=Hintjens|first=Pieter|date=7 February 2006|publisher=iMatix Corporation|access-date=18 February 2018}}</ref> AMQP was conceived as a co-operative open effort. The initial design was by JPMorgan Chase from mid-2004 to mid-2006 and it contracted [[iMatix Corporation]] to develop a C broker and protocol documentation. In 2005 JPMorgan Chase approached other firms to form a working group that included [[Cisco Systems]], [[IONA Technologies]], iMatix, [[Red Hat]], and [[Transaction Workflow Innovation Standards Team]] (TWIST). In the same year JPMorgan Chase partnered with Red Hat to create [[Apache Qpid]], initially in Java and soon after C++. Independently, [[RabbitMQ]] was developed in [[Erlang (programming language)|Erlang]] by Rabbit Technologies, followed later by the [[Microsoft]] and StormMQ implementations.

The working group grew to 23 companies including [[Bank of America]], [[Barclays]], Cisco Systems, [[Credit Suisse]], [[Deutsche Börse]], [[Goldman Sachs]], [[HCL Technologies| HCL Technologies Ltd]], [[Progress Software]], [[IIT Software]], [[INETCO Systems Limited]], [[Informatica]] (including 29 West), JPMorgan Chase, [[Microsoft| Microsoft Corporation]], my-Channels, [[Novell]], [[Red Hat]], [[Software AG]], [[Solace systems|Solace Systems]], StormMQ, [[Tervela| Tervela Inc.]], TWIST Process Innovations ltd, [[VMware]] (which acquired Rabbit Technologies) and [[WSO2]].

In 2008, [[Pieter Hintjens]], CEO and chief software designer of iMatix, wrote an article called "What is wrong with AMQP (and how to fix it)"<ref>{{Cite web |last=Hintjens |first=Pieter |title=What is wrong with AMQP (and how to fix it) |url=http://www.imatix.com/articles:whats-wrong-with-amqp |archive-url=https://web.archive.org/web/20110906085106/http://www.imatix.com/articles:whats-wrong-with-amqp |archive-date=2011-09-06 |access-date=2024-03-01 |website=iMatix}}</ref> and distributed it to the working group to alert of imminent failure, identify problems seen by iMatix and propose ways to fix the AMQP specification. By then, iMatix had already started work on [[ZeroMQ]]. In 2010, Hintjens announced that iMatix would leave the AMQP workgroup and did not plan to support AMQP/1.0 in favor of the significantly simpler and faster ZeroMQ.<ref>{{Cite web |last=Hintjens |first=Pieter |date=2010-03-30 |title=iMatix will end OpenAMQ support by 2011 |url=http://lists.openamq.org/pipermail/openamq-dev/2010-March/001598.html |url-status=usurped |archive-url=https://web.archive.org/web/20100402070046/http://lists.openamq.org/pipermail/openamq-dev/2010-March/001598.html |archive-date=2010-04-02 |access-date=2024-03-01 |website=openamq-dev mailing list}}</ref>

In August 2011, the AMQP working group announced its reorganization into an [[OASIS (organization)|OASIS]] member section.<ref>{{Cite web |url=http://www.amqp.org/node/54 |title=AMQP Working Group Transitions to OASIS Member Section |access-date=28 January 2012 |archive-url=https://web.archive.org/web/20120416223525/http://www.amqp.org/node/54 |archive-date=16 April 2012 |url-status=dead }}</ref>

AMQP 1.0 was released by the AMQP working group on 30 October 2011, at a conference in New York. At the event Microsoft, Red Hat, [[VMware]], Apache, INETCO and IIT Software demonstrated software running the protocol in an interoperability demonstration. The next day, on 1 November 2011, the formation of an [[OASIS (organization)|OASIS]] Technical Committee was announced<ref>[http://www.amqp.org/node/58 OASIS Forms AMQP Technical Committee to Advance Business Messaging Interoperability Within Middleware, Mobile, and Cloud Environments]</ref> to advance this contributed AMQP version 1.0 through the international open standards process. The first draft from OASIS was released in February 2012,<ref>{{cite news|title=30-day Public Review for OASIS AMQP Version 1.0|url=https://www.oasis-open.org/news/announcements/pr-30-day-public-review-for-oasis-amqp-version-1-0|access-date=18 June 2012|date=21 February 2012}}</ref> the changes as compared to that published by the Working Group being restricted to edits for improved clarity (no functional changes). The second draft was released for public review on 20 June (again with no functional changes),<ref>{{cite news|title=15 day Public Review for OASIS AMQP Version 1.0|url=https://www.oasis-open.org/news/announcements/15-day-public-review-for-oasis-amqp-version-1-0|access-date=20 June 2012|date=20 June 2012}}</ref> and AMQP was approved as an OASIS standard on 31 October 2012.<ref>{{cite news|title=AMQP 1.0 Becomes OASIS Standard|url=https://www.oasis-open.org/news/pr/amqp-1-0-approval|access-date=1 November 2012|date=31 October 2012}}</ref>

OASIS AMQP was approved for release as an ISO and IEC International Standard in April 2014.<ref>{{cite web|title=Information technology -- Advanced Message Queuing Protocol (AMQP) v1.0 specification|url=https://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=64955|work=ISO/IEC 19464|publisher=ISO|access-date=1 May 2014}}</ref> AMQP 1.0 was balloted through the Joint Technical Committee on Information Technology (JTC1) of the International Standards Organization (ISO) and the International Electrotechnical Commission (IEC). The approved OASIS AMQP submission has been given the designation, ISO/IEC 19464.

Previous versions of AMQP were 0-8, published in June 2006, 0-9, published in December 2006, 0-10 published in February 2008<ref>{{cite web|title=AMQP PMC Meeting Minutes 13th February, 2008|url=http://77.95.34.224/confluence/display/AMQP/PMC+Minutes+for+2008-02-13|archive-url=https://archive.today/20121130171127/http://77.95.34.224/confluence/display/AMQP/PMC+Minutes+for+2008-02-13|url-status=dead|archive-date=30 November 2012|work=AMQP PMC Minutes|publisher=AMQP Working Group|access-date=15 June 2012}}</ref> and 0-9-1, published in November 2008. These earlier releases are significantly different from the 1.0 specification.<ref>{{Cite web|url=https://www.rabbitmq.com/amqp-0-8-to-0-9-1.html|title=RabbitMQ - AMQP 0-8 to 0-9-1|website=www.rabbitmq.com|access-date=2018-01-12}}</ref><ref>{{Citation|title=rabbitmq-amqp1.0: AMQP 1.0 support for RabbitMQ|date=2017-12-17|url=https://github.com/rabbitmq/rabbitmq-amqp1.0|publisher=RabbitMQ|access-date=2018-01-12}}</ref>

Whilst AMQP originated in the financial services industry, it has general applicability to a broad range of [[middleware]] problems.

== Description of AMQP 1.0 ==

=== Type system ===

AMQP defines a [[self-describing]] encoding scheme allowing interoperable representation of a wide range of commonly used types. It also allows typed data to be [[semantic annotation|annotated]] with additional meaning,<ref>{{cite web|title=OASIS AMQP version 1.0, section 1.1|url=https://docs.oasis-open.org/amqp/core/v1.0/amqp-core-types-v1.0.html#section-types|publisher=OASIS AMQP Technical Committee|access-date=18 June 2012}}</ref> for example a particular string value might be annotated so that it could be understood as a [[URL]]. Likewise a map value containing key-value pairs for 'name', 'address' etc., might be annotated as being a representation of a 'customer' type.

The type-system is used to define a message format allowing standard and extended meta-data to be expressed and understood by processing entities. It is also used to define the communication primitives through which messages are exchanged between such entities, i.e. the AMQP ''frame bodies''.

=== Performatives and the link protocol ===

The basic unit of data in AMQP is a ''frame''. There are nine AMQP frame bodies defined that are used to initiate, control and tear down the transfer of messages between two peers. These are:

* open (the ''connection'')
* begin (the ''session'')
* attach (the ''link'')
* transfer
* flow
* disposition
* detach (the ''link'')
* end (the ''session'')
* close (the ''connection'')

The ''link protocol'' is at the heart of AMQP.

An ''attach'' frame body is sent to initiate a new link; a ''detach'' to tear down a link. Links may be established in order to receive or send messages.

Messages are sent over an established ''link'' using the ''transfer'' frame. Messages on a link flow in only one direction.

Transfers are subject to a credit-based flow control scheme, managed using ''flow'' frames. This allows a process to protect itself from being overwhelmed by too large a volume of messages or more simply to allow a subscribing link to pull messages as and when desired.<ref>{{cite web|title=OASIS AMQP version 1.0, section 2.6.7-2.6.9|url=https://docs.oasis-open.org/amqp/core/v1.0/amqp-core-transport-v1.0.html#doc-flow-control|publisher=OASIS AMQP Technical Committee|access-date=18 June 2012}}</ref>

Each transferred message must eventually be ''settled''. Settlement ensures that the sender and receiver agree on the state of the transfer, providing reliability guarantees. Changes in state and settlement for a transfer (or set of transfers) are communicated between the peers using the ''disposition'' frame. Various reliability guarantees can be enforced this way: at-most-once, at-least-once and exactly-once.<ref>{{cite web|title=OASIS AMQP version 1.0, section 2.6.12-2.6.14|url=https://docs.oasis-open.org/amqp/core/v1.0/amqp-core-transport-v1.0.html#doc-idp489648|publisher=AMQP WorkingGroup|access-date=18 June 2012}}</ref>

Multiple links, in both directions, can be grouped together in a ''session''. A session is a bidirectional, sequential conversation between two peers that is initiated with a ''begin'' frame and terminated with an ''end'' frame. A connection between two peers can have multiple sessions multiplexed over it, each logically independent. Connections are initiated with an ''open'' frame in which the sending peer's capabilities are expressed, and terminated with a ''close'' frame.

=== Message format ===

AMQP defines as the ''bare message'', that part of the message that is created by the sending application. This is considered immutable as the message is transferred between one or more processes.

Ensuring the message as sent by the application is immutable allows for end-to-end message signing and/or [[end-to-end encryption|encryption]] and ensures that any integrity checks (e.g. hashes or [[Cryptographic hash function|digests]]) remain valid. The message can be annotated by intermediaries during transit, but any such annotations are kept distinct from the immutable ''bare message''. Annotations may be added before or after the bare message.

The ''header'' is a standard set of delivery-related annotations that can be requested or indicated for a message and includes time to live, durability, priority.<ref>{{cite web|title=OASIS AMQP version 1.0, section 3.2.1|url=https://docs.oasis-open.org/amqp/core/v1.0/amqp-core-messaging-v1.0.html#type-header|publisher=OASIS AMQP Technical Committee|access-date=18 June 2012}}</ref>

The bare message itself is structured as an optional list of standard properties (message id, user id, creation time, reply to, subject, correlation id, group id etc.), an optional list of
application-specific properties (i.e., extended properties) and a body, which AMQP refers to as application data.<ref>{{cite web|title=OASIS AMQP version 1.0, section 3.2|url=https://docs.oasis-open.org/amqp/core/v1.0/amqp-core-messaging-v1.0.html#section-message-format|publisher=OASIS AMQP Technical Committee|access-date=18 June 2012}}</ref>

Properties are specified in the AMQP type system, as are annotations. The application data can be of any form, and in any encoding the application chooses. One option is to use the AMQP type system to send structured, self-describing data.

=== Messaging capabilities ===

The link protocol transfers messages between two ''nodes'' but assumes very little as to what those nodes are or how they are implemented.

A key category is those nodes used as a ''rendezvous point'' between senders and receivers of messages (e.g. ''queues'' or ''topics''). The AMQP specification calls such nodes ''distribution nodes'' and codifies some common behaviors.<ref>{{cite web|title=OASIS AMQP version 1.0, section 3.3|url=https://docs.oasis-open.org/amqp/core/v1.0/amqp-core-messaging-v1.0.html#section-distribution-nodes|publisher=OASIS AMQP Technical Committee|access-date=15 June 2012}}</ref>

This includes:

* some standard outcomes for transfers, through which receivers of messages can for example accept or reject messages <ref>{{cite web|title=OASIS AMQP version 1.0, section 3.4|url=https://docs.oasis-open.org/amqp/core/v1.0/amqp-core-messaging-v1.0.html#section-delivery-state|publisher=OASIS AMQP Technical Committee|access-date=18 June 2012}}</ref>
* a mechanism for indicating or requesting one of the two basic distribution patterns, competing- and non-competing- consumers, through the ''distribution modes'' ''move'' and ''copy'' respectively <ref>{{cite web|title=OASIS AMQP version 1.0, section 3.5.2|url=https://docs.oasis-open.org/amqp/core/v1.0/amqp-core-messaging-v1.0.html#doc-idp383328|publisher=OASIS AMQP Technical Committee|access-date=18 June 2012}}</ref>
* the ability to create nodes on-demand,<ref>{{cite web|title=OASIS AMQP version 1.0, section 3.5.3|url=https://docs.oasis-open.org/amqp/core/v1.0/amqp-core-messaging-v1.0.html#type-source|publisher=OASIS AMQP Technical Committee|access-date=18 June 2012}}</ref><ref>{{cite web|title=OASIS AMQP version 1.0, section 3.5.4|url=https://docs.oasis-open.org/amqp/core/v1.0/amqp-core-messaging-v1.0.html#type-target|publisher=OASIS AMQP Technical Committee|access-date=18 June 2012}}</ref> e.g. for temporary response queues
* the ability to refine the set of message of interest to a receiver through filters <ref>{{cite web|title=OASIS AMQP version 1.0, section 3.5.1|url=https://docs.oasis-open.org/amqp/core/v1.0/amqp-core-messaging-v1.0.html#doc-idp381376|publisher=OASIS AMQP Technical Committee|access-date=18 June 2012}}</ref>

Though AMQP can be used in simple peer-to-peer systems, defining this framework for messaging capabilities additionally enables interoperability with messaging intermediaries (brokers, bridges etc.)
in larger, richer messaging networks. The framework specified covers basic behaviors but allows for extensions to evolve that can be further codified and standardised.

== Implementations ==

=== AMQP 1.0 broker implementations ===
* [[Apache Qpid]], an [[open-source software|open-source]] project at the [[Apache Foundation]]
* [[Apache ActiveMQ]], an [[open-source software|open-source]] project at the [[Apache Foundation]]
* [[Microsoft Azure|Azure]] Event Hubs<ref name="azure-and-event-hubs">{{Cite web|url=https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-amqp-protocol-guide|title=AMQP 1.0 in Azure Service Bus and Event Hubs protocol guide|last=axisc|website=docs.microsoft.com|language=en-us|access-date=2019-05-21}}</ref><ref>{{Cite web|url=https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-about|title=What is Azure Event Hubs? - a Big Data ingestion service|last=ShubhaVijayasarathy|website=docs.microsoft.com|language=en-us|access-date=2019-05-21}}</ref>
* [[Microsoft Azure|Azure]] Service Bus<ref name="azure-and-event-hubs"/><ref>{{Cite web|url=https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-amqp-overview|title=Overview of AMQP 1.0 in Azure Service Bus|last=axisc|website=docs.microsoft.com|language=en-us|access-date=2019-05-21}}</ref>
* [[IBM MQ]]<ref>{{Cite web |title=IBM MQ |url=https://www.ibm.com/products/mq |access-date=2024-03-15 |website=www.ibm.com |language=en-us}}</ref><ref>{{Cite web |title=About IBM MQ |url=https://www.ibm.com/docs/en/ibm-mq/9.3?topic=mq-about |access-date=2024-03-15 |website=www.ibm.com |language=en-us}}</ref>
* [[Solace Corporation|Solace]] PubSub+, a multi-protocol broker in hardware, software, and cloud<ref>{{cite web |url=https://www.solace.com |title=Solace PubSub+ |work=solace.com}}</ref>
* [[RabbitMQ]], an [[open-source software|open-source]] project sponsored by [[VMware]], supports AMQP 1.0 with release 4.0

=== Pre-1.0 AMQP broker implementations ===
* [[JORAM]], a Java [[open-source software|open-source]] implementation from the [[OW2 Consortium]].
* [[Apache Qpid]] maintains support for multiple AMQP versions<ref>{{usurped|1=[https://web.archive.org/web/20130914045254/http://qpid.apache.org/releases/qpid-0.22/index.html Qpid 0.22 - Apache Qpid]}}</ref>

== Specification ==

AMQP protocol version 1.0 is the current specification version. It focuses on core features which are necessary for interoperability at Internet scale. It contains less explicit routing than previous versions because core functionality is the first to be rigorously standardized. AMQP 1.0 interoperability has been more extensively tested with more implementors than prior versions.<ref>{{cite web|title=Status of Pre-1.0 Versions of AMQP|url=http://www.amqp.org/resources/download|publisher=AMQP site|access-date=28 May 2014}}</ref>

The AMQP website contains the {{usurped|1=[https://web.archive.org/web/20141010172100/http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-overview-v1.0-os.html OASIS specification for version 1.0]}}.

Earlier versions of AMQP, published prior to the release of 1.0 (see History above) and significantly different from it, include:
* [https://www.amqp.org/specification/0-9-1/amqp-org-download AMQP 0-9-1], which has clients available "for many popular programming languages and platforms"<ref>{{cite web|title=AMQP 0-9-1 Model Explained|url=https://www.rabbitmq.com/tutorials/amqp-concepts.html|publisher=VMWare, Inc.|access-date=1 November 2012}}</ref>
* [https://www.amqp.org/specification/0-10/amqp-org-download AMQP 0-10]

== Comparable specifications ==
These open protocol specifications cover the same or a similar space as AMQP:
* [[Streaming Text Oriented Messaging Protocol]] (STOMP), a text-based protocol developed at Codehaus; uses the JMS-like semantics of 'destination'.
* [[Extensible Messaging and Presence Protocol]] (XMPP), the Extensible Messaging and Presence Protocol.
* [[MQTT]], a lightweight publish-subscribe protocol.
* [[OpenWire (binary protocol)|OpenWire]] as used by [[ActiveMQ]].

[[Java Message Service]] (JMS), is often compared to AMQP. However, JMS is an API specification (part of the [[Java Platform, Enterprise Edition|Java EE]] specification) that defines how message producers and consumers are implemented. JMS does not guarantee interoperability between implementations, and the JMS-compliant [[Enterprise messaging system|messaging system]] in use may need to be deployed on both client and server. On the other hand, AMQP is a wire-level protocol specification. In theory AMQP provides interoperability as different AMQP-compliant software can be deployed on the client and server sides.

== See also ==
* [[Peer-to-peer]]
* [[Message queue]]
* [[Message queuing service]]
* [[Data Distribution Service]]
* [[IBM MQ]]

== References ==
{{Reflist|30em}}

== External links ==
* {{official website}}
* [https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=amqp OASIS AMQP technical committee]
* [https://www.rabbitmq.com/tutorials/amqp-concepts.html High-level Overview of AMQP and the AMQP Model (version 0-9-1)]
* [http://www.omg.org/news/meetings/workshops/RT-2007/04-3_Pardo-Castellote-revised.pdf OMG Analysis of AMQP and comparison with DDS-RTPS]
* [https://google-ukdev.blogspot.com/2008/09/rabbitmq-tech-talk-at-google-london.html Google Tech Talk, with video and slides, about RabbitMQ]
* [http://www.slideshare.net/pieterh/fosdem-2009 Presentation of AMQP and RestMS messaging at FOSDEM 2009]
* [https://www.rabbitmq.com/devtools.html List of AMQP clients]

{{OASIS Standards}}

[[Category:Application layer protocols]]
[[Category:Inter-process communication]]
[[Category:Message-oriented middleware]]
[[Category:Middleware]]
[[Category:Open standards]]

Advanced Message Queuing Protocol - Revision history

imported>SchlurcherBot: Bot: http → https