debian/0000755000000000000000000000000012172756430007175 5ustar debian/control0000644000000000000000000000164512172756345010613 0ustar Source: amqp-specs Section: net Priority: optional Maintainer: Jonas Smedegaard Build-Depends: cdbs, devscripts, debhelper, dh-buildinfo Standards-Version: 3.9.4 Homepage: http://www.amqp.org/ Vcs-Git: git://git.debian.org:/git/collab-maint/amqp-specs Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/amqp-specs.git Package: amqp-specs Architecture: all Depends: ${misc:Depends} Description: specs for the Advanced Message Queuing Protocol (AMQP) AMQP is the Internet Protocol for Business Messaging . The Advanced Message Queuing Protocol (AMQP) is an open standard for passing business messages between applications or organizations. It connects systems, feeds business processes with the information they need and reliably transmits onward the instructions that achieve their goals. . This package provides current and legacy AMQP protocol specifications, needed by some implementations. debian/source/0000755000000000000000000000000012055253117010467 5ustar debian/source/format0000644000000000000000000000001411316654760011705 0ustar 3.0 (quilt) debian/changelog0000644000000000000000000000071112172756430011046 0ustar amqp-specs (1-0r0-2) unstable; urgency=low * Add 0-9-1-rabbit spec from rabbitmq.com. * Add 0-10 and *-qpid specs from qpid.apache.org. * Mention explicitly in source package the source URL for legacy specs. -- Jonas Smedegaard Sun, 21 Jul 2013 15:07:13 +0200 amqp-specs (1-0r0-1) unstable; urgency=low * Initial packaging release. Closes: bug#705761. -- Jonas Smedegaard Sat, 20 Apr 2013 11:58:48 +0200 debian/README.source0000644000000000000000000000056312121764047011355 0ustar CDBS+git-buildpackage --------------------- This source package uses CDBS and git-buildpackage. NMUs need not (but are encouraged to) make special use of these tools. In particular, the debian/control.in file can be completely ignored. More info here: http://wiki.debian.org/CDBS+git-buildpackage -- Jonas Smedegaard Mon, 18 Feb 2013 12:55:37 +0100 debian/legacy/0000755000000000000000000000000012172722064010435 5ustar debian/legacy/README0000644000000000000000000000011212172722064011307 0ustar These files was downloaded from . debian/legacy/amqp0-9.stripped.xml0000644000000000000000000010556711716765774014234 0ustar debian/legacy/amqp0-8.stripped.xml0000644000000000000000000007545711716766020014220 0ustar debian/legacy/amqp0-9-1.stripped.xml0000644000000000000000000004675111716765732014363 0ustar debian/README.Debian0000644000000000000000000000040112134442732011224 0ustar AMQP specs for Debian --------------------- Legacy protocol specification 0-10 is not included with this package, because that revision have not been released under a DFSG-free license. -- Jonas Smedegaard Fri, 19 Apr 2013 19:53:07 +0200 debian/compat0000644000000000000000000000000212055253147010370 0ustar 8 debian/watch0000644000000000000000000000026712134275670010233 0ustar # Run the "uscan" command to check for upstream updates and more. version=3 #opts=uversionmangle=s/[-r]/./ \ http://www.amqp.org/resources/download .*/files/amqp-(\d.*)-stripped\.tgz debian/copyright_hints0000644000000000000000000000437412172756326012351 0ustar Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Upstream-Name: FIXME Upstream-Contact: FIXME Source: FIXME Disclaimer: Autogenerated by CDBS Files: debian/Qpid/README debian/README.Debian debian/README.source debian/RabbitMQ/README debian/compat debian/control debian/control.in debian/gbp.conf debian/install debian/legacy/README debian/source/format debian/watch Copyright: *No copyright* License: UNKNOWN FIXME Files: debian/Qpid/amqp-dtx-preview.0-9.xml debian/Qpid/amqp-errata.0-9.xml debian/Qpid/amqp-nogen.0-9.xml debian/Qpid/amqp.xsl debian/Qpid/apache-filters.xml debian/Qpid/cluster.0-8.xml debian/Qpid/management-schema.xml Copyright: ownership. The ASF licenses this file License: Apache-2.0 FIXME Files: debian/Qpid/amqp0-8.stripped.xml debian/Qpid/amqp0-9-1.stripped.xml debian/Qpid/amqp0-9.stripped.xml debian/legacy/amqp0-8.stripped.xml debian/legacy/amqp0-9-1.stripped.xml debian/legacy/amqp0-9.stripped.xml Copyright: 2009, AMQP Working Group License: BSD-3-clause FIXME Files: index.bare.xml messaging.bare.xml security.bare.xml transactions.bare.xml transport.bare.xml types.bare.xml Copyright: Bank of America, N.A., Barclays Bank PLC, Cisco Systems, Credit License: BSD-3-clause FIXME Files: debian/Qpid/amqp.0-10-qpid-errata.stripped.xml debian/Qpid/amqp.0-10.stripped.xml Copyright: 2009, AMQP Working Group Cisco Systems, Credit Suisse, Deutsche Borse Systems License: BSD-3-clause FIXME Files: debian/Qpid/amqp0-8-qpid.stripped.xml debian/Qpid/amqp0-9-qpid.stripped.xml Copyright: 2009, AMQP Working Group JPMorgan Chase Bank & Co., Cisco Systems, Inc., Envoy License: BSD-3-clause FIXME Files: debian/Qpid/LICENSE Copyright: You must retain, in the Source form of any Derivative Works [yyyy license to reproduce, prepare Derivative Works of owner owner. For the purposes of this definition, "submitted" License: Apache-2.0 FIXME Files: debian/RabbitMQ/amqp0-9-1.stripped.extended.xml Copyright: 2009, AMQP Working Group 2010-2013, VMware, Inc. and may be distributed License: BSD-3-clause FIXME Files: debian/rules Copyright: 2013, Jonas Smedegaard License: GPL-3+ FIXME Files: debian/Qpid/NOTICE Copyright: 2006-2008, Apache Software Foundation License: UNKNOWN FIXME debian/copyright0000644000000000000000000000770312172740062011131 0ustar Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Upstream-Name: AMQP Protocol Upstream-Contact: http://www.amqp.org/contact Source: http://www.amqp.org/resources/download http://www.rabbitmq.com/protocol.html Files: * Copyright: 2006-2011, Bank of America, N.A. 2006-2011, Barclays Bank PLC 2006-2011, Cisco Systems 2006-2011, Credit Suisse 2006-2011, Deutsche Boerse 2006-2011, Envoy Technologies Inc. 2006-2011, Goldman Sachs 2006-2011, HCL Technologies Ltd 2006-2011, IIT Software GmbH 2006-2011, iMatix Corporation 2006-2011, INETCO Systems Limited 2006-2011, Informatica Corporation 2006-2011, JPMorgan Chase & Co. 2006-2011, Kaazing Corporation, N.A 2006-2011, Microsoft Corporation 2006-2011, my-Channels 2006-2011, Novell 2006-2011, Progress Software 2006-2011, Red Hat Inc. 2006-2011, Software AG 2006-2011, Solace Systems Inc. 2006-2011, StormMQ Ltd. 2006-2011, Tervela Inc. 2006-2011, TWIST Process Innovations Ltd 2006-2011, VMware, Inc. 2006-2011, WS02 Inc. License: BSD-3-clause Files: debian/* Copyright: 2012, Jonas Smedegaard License: GPL-3+ Files: debian/legacy/* debian/RabbitMQ/* Copyright: 2009, AMQP Working Group License: BSD-3-clause Files: debian/RabbitMQ/* Copyright: 2009, AMQP Working Group 2010-2013 VMware, Inc. License: BSD-3-clause Files: debian/Qpid/* Copyright: 2006-2008 Apache Software Foundation License: Apache-2.0 Files: debian/Qpid/*.stripped.* Copyright: 2006-2007, 29West Inc. 2006-2007, Cisco Systems 2006-2007, Credit Suisse 2006-2007, Deutsche Borse Systems 2006-2007, Envoy Technologies, Inc. 2006-2007, Goldman Sachs 2006-2007, iMatix Corporation sprl. 2006-2007, IONA Technologies PLC 2006-2007, JPMorgan Chase Bank Inc. N.A 2006-2007, Novell 2006-2007, Rabbit Technologies Ltd. 2006-2007, Red Hat, Inc. 2006-2007, TWIST Process Innovations ltd 2009, AMQP Working Group License: BSD-3-clause License: BSD-3-clause Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission. . THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. License: Apache-2.0 Comment: . On Debian systems the 'Apache License' version 2.0 is located in '/usr/share/common-licenses/Apache-2.0'. License: GPL-3+ This file 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. . Comment: . On Debian systems the 'GNU General Public License' version 3 is located in '/usr/share/common-licenses/GPL-3'. . You should have received a copy of the GNU General Public License along with this program. If not, see . debian/install0000644000000000000000000000115112172742224010560 0ustar *.xml /usr/share/amqp/specs/1-0 debian/legacy/amqp0-9-1.* /usr/share/amqp/specs/0-9-1 debian/legacy/amqp0-9.* /usr/share/amqp/specs/0-9 debian/legacy/amqp0-8.* /usr/share/amqp/specs/0-8 debian/RabbitMQ/amqp0-9-1.stripped.extended.xml /usr/share/amqp/specs/0-9-1-rabbit debian/Qpid/amqp0-8-qpid.stripped.xml /usr/share/amqp/specs/0-8-qpid debian/Qpid/amqp0-9-qpid.stripped.xml /usr/share/amqp/specs/0-9-qpid debian/Qpid/amqp0-9-1.stripped.xml /usr/share/amqp/specs/0-9-1-qpid debian/Qpid/amqp.0-10.stripped.xml /usr/share/amqp/specs/0-10 debian/Qpid/amqp.0-10-qpid-errata.stripped.xml /usr/share/amqp/specs/0-10-qpid debian/RabbitMQ/0000755000000000000000000000000012172721071010627 5ustar debian/RabbitMQ/README0000644000000000000000000000011112172710105011474 0ustar These files was downloaded from . debian/RabbitMQ/amqp0-9-1.stripped.extended.xml0000644000000000000000000005401712172035173016333 0ustar debian/gbp.conf0000644000000000000000000000014612134276246010615 0ustar # Configuration file for git-buildpackage and friends [DEFAULT] pristine-tar = True sign-tags = True debian/rules0000755000000000000000000000267312172736615010270 0ustar #!/usr/bin/make -f # -*- mode: makefile; coding: utf-8 -*- # Copyright © 2013 Jonas Smedegaard # Description: Main Debian packaging script for AMQP Protocol # # This program 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, or (at your option) # any later version. # # This program 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 . DEB_BUILDDIR = build include /usr/share/cdbs/1/rules/upstream-tarball.mk include /usr/share/cdbs/1/rules/utils.mk include /usr/share/cdbs/1/rules/debhelper.mk pkg = $(DEB_UPSTREAM_PACKAGE) DEB_UPSTREAM_URL = http://www.amqp.org/sites/amqp.org/files DEB_UPSTREAM_TARBALL_BASENAME = amqp-$(DEB_UPSTREAM_TARBALL_VERSION)-stripped DEB_UPSTREAM_TARBALL_EXTENSION = tgz DEB_UPSTREAM_RECEIVED_EXTENSION = tar DEB_UPSTREAM_TARBALL_MD5 = abe24d75f16dfdb02401fbb6d9a3b810 get-orig-source: get-orig-source-qpid get-orig-source-qpid: wget -m -np -nd -R amqp.0-10.dtd,index.html -P debian/Qpid https://svn.apache.org/repos/asf/qpid/trunk/qpid/specs/ rm -f debian/Qpid/robots.txt debian/Qpid/0000755000000000000000000000000012172747602010073 5ustar debian/Qpid/README0000644000000000000000000000022512172747602010752 0ustar These files was downloaded from , referenced at . debian/Qpid/amqp-nogen.0-9.xml0000644000000000000000000000261412112735427013162 0ustar debian/Qpid/amqp0-9-qpid.stripped.xml0000644000000000000000000011030712140553074014560 0ustar debian/Qpid/NOTICE0000644000000000000000000000043712112735427010777 0ustar // ------------------------------------------------------------------ // NOTICE file corresponding to the section 4d of The Apache License, // Version 2.0, // ------------------------------------------------------------------ Apache Qpid Copyright 2006-2008 Apache Software Foundation debian/Qpid/management-schema.xml0000644000000000000000000011056012162631717014170 0ustar This class represents an inter-broker connection. debian/Qpid/amqp.xsl0000644000000000000000000007541212112735427011566 0ustar AMQP <xsl:call-template name="initCap"><xsl:with-param name="input" select="@name"/></xsl:call-template>

AMQP

Table of Contents

 #section- #doc-        #-             

← section-

←doc-

← doc-
pre #section- #type- #doc- .xml

← type-

signature : Encodings: composite

← type-

composite fields mandatory optional []

← type-

compositepossible values anchorchoice--
<type name="" class="" source="" provides=""/> </type>
<descriptor name="" code=""/> <choice =""/> <field =""/> </field> <error =""/> code : fixed-width, byte value variable-width, byte size
#type-
TypeEncodingCodeCategoryDescription
#type- /
error:

← definition-

signature : . .. . * #type- .xml #type- #choice-- .xml #choice-- debian/Qpid/amqp.0-10-qpid-errata.stripped.xml0000644000000000000000000013623412140471333016166 0ustar
debian/Qpid/amqp-errata.0-9.xml0000644000000000000000000000332512112735427013332 0ustar This flag tells the server how to react if the message cannot be routed to a queue. If this flag is set, the server will return an unroutable message with a Return method. If this flag is zero, the server silently drops the message. debian/Qpid/amqp0-9.stripped.xml0000644000000000000000000010556712140515561013640 0ustar debian/Qpid/apache-filters.xml0000644000000000000000000002704112156133074013502 0ustar

Versions of AMQP prior to 1.0 prescribed a model of Exchanges and Queues, where Queues were bound to Exchanges with a binding key whose meaning depended upon the type of the Exchange. In order to allow a consistent mechanism for addressing legacy AMQP Exchanges over AMQP 1.0 the following filter types are defined. Use of an Exchange as an address for a Source thus can be seen as equivalent to constructing exclusive queues bound to an Exchange in legacy AMQP versions.

Containers which support the filters that are defined in this section should advertise the capability APACHE.ORG:LEGACY_AMQP_EXCHANGE_FILTERS in their connection capabilities when sending the open performative, and MUST provide this capability on sources supporting these filter types.

The legacy-amqp-direct-binding filter consists of a described string value. The filter matches a message if and only if the described string value exactly matches the subject field of the Properties section of the message being evaluated. If the message has no Properties section, or if the subject field of the Properties section is not set, then the legacy-amqp-direct-binding filter does not match.

The legacy-amqp-topic-binding filter consists of a described string value. The value value described by the type is interpreted as a pattern to match against the subject field of the Properties section of the message being evaluated.

  • The pattern is formed using zero or more tokens, with each token delimited by the "." character. The tokens "#" and "*" have special meanings.
  • The token consisting of the single character "*" matches a single word in the subject field.
  • The token consisting of the single character "#" matches zero or more words in the subject field.

Thus the filter value "*.stock.#" would match the subjects "usd.stock" and "eur.stock.db" but not "stock.nasdaq".

If the message has no Properties section, or if the subject field of the Properties section is not set, then the legacy-amqp-topic-binding filter matches only if the value of the filter is a single "#".

The legacy-amqp-headers-binding filter consists of a described map value. The map value described by the type is interpreted as a pattern to match against the application-properties section of the message being evaluated. The map has the same restriction as the application-properties section, namely that the keys of this are restricted to be of type string (which excludes the possibility of a null key) and the values are restricted to be of simple types only, that is, excluding map, list, and array types.

The key "x-match" in the described map has special meaning. This key MUST map to the symbolic value "any" or the symbolic value "all" within the described map. All other keys which begin "x-" MUST be ignored by the source when evaluating. If the value for "x-match" is "all" then all other valid key-value pairs in the map MUST match with an entry with the same key in the application-properties section. If the value for "x-match" is "any" then the filter will accept the message if at least one key-value pair matches the equivalent key value pair in the application-properties section.

A key-value pair in the filter's map matches a key-value pair in the application-properties section if the keys are identical (including the same type), or if the value in the filter map for the key is null.

The Java Message Service defines two types of filtering of messages: firstly the ability to exclude from a subscription messages sent by the same connection, secondly a more general filtering syntax known as "selectors" based on an SQL like syntax.

AMQP filter extensions through which these two types of filtering may be achieved are defined below. Their use, though motivated by support for JMS, is not restricted to JMS.

A message will be accepted by the simple-no-local-filter if and only if the message was originally sent to the container of the source on a separate connection from that which is currently receiving from the source.

Containers which support this filter should advertise the capability APACHE.ORG:NO_LOCAL in their connection capabilities when sending the open performative, and MUST provide this capability on sources supporting these filter types.

The Java Message Service "selector" defines an SQL like syntax for filtering messages. The selector filters based on the values of "headers" and "properties". The selector-filter uses the selector as defined by JMS but with the names of JMS headers translated into their AMQP equivalents. The defined JMS headers can be mapped to equivalent fields within the AMQP message sections:

JMS Header Name | AMQP 1.0 Field ==================|==================================================== JMSCorrelationID | correlation-id field of properties section JMSDeliveryMode | durable field of header section JMSDestination | to field of the properties section JMSExpiration | absolute-expiry-time of properties section JMSMessageID | message-id of properties section JMSPriority | priority field of header section JMSRedelivered | delivery-count > 0 in header section JMSReplyTo | reply-to in properties section JMSTimestamp | creation-time of properties section JMSType | annotation jms-type in message-annotations section

When encoding the selector string on the wire, these JMS header names should be translated to amqp.field_name where field_name is the appropriate AMQP 1.0 field named in the table above, with the hyphen replaced by an underscore. For example, the selector: "JMSCorrelationID = 'abc' AND color = 'blue' AND weight > 2500" would be transferred over the wire as: "amqp.correlation_id = 'abc' AND color = 'blue' AND weight > 2500"

The "properties" of the JMS message are equivalent to the AMQP application-properties section. Thus a reference to a property Foo in a message selector would be evaluated as the value associated with the key "Foo" (if present) in the application-properties section.

The operands of the JMS selector are defined in terms of the types available within JMS, When evaluated against the application properties section, the values within that section MUST be evaluated according to the following type mapping.

AMQP Type | JMS Selector Type ==================|=================== null | null boolean | boolean ubyte | short ushort | int uint | long ulong | long byte | byte short | short int | int long | long float | float double | double decimal32 | double decimal64 | double decimal128 | double char | char timestamp | long uuid | byte[16] binary | byte[] string | String symbol | String

Containers which support this filter should advertise the capability APACHE.ORG:SELECTOR in their connection capabilities when sending the open performative, and MUST provide this capability on sources supporting these filter types.

The xquery filter consists of a described string value containing a valid xquery string against which messages are matched.

Containers which support the filter defined in this section should advertise the capability APACHE.ORG:XQUERY in their connection capabilities when sending the open performative.

debian/Qpid/amqp0-8.stripped.xml0000644000000000000000000007545712140515561013643 0ustar debian/Qpid/amqp0-9-1.stripped.xml0000644000000000000000000005044112112735427013770 0ustar debian/Qpid/amqp.0-10.stripped.xml0000644000000000000000000013604712140470750013763 0ustar
debian/Qpid/cluster.0-8.xml0000644000000000000000000000334412112735427012601 0ustar An extension that allows brokers to communicate in order to provide a clustered service to clients. debian/Qpid/amqp0-8-qpid.stripped.xml0000644000000000000000000007767512140553074014603 0ustar debian/Qpid/LICENSE0000644000000000000000000002613612140721717011102 0ustar Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. debian/Qpid/amqp-dtx-preview.0-9.xml0000644000000000000000000012171712112735427014340 0ustar The rollback was caused by an unspecified reason. A transaction branch took too long. The transaction branch may have been heuristically completed. The transaction branch has been heuristically committed. The transaction branch has been heuristically rolled back. The transaction branch has been heuristically committed and rolled back. The transaction branch was read-only and has been committed. Normal execution. An Xid uniquely identifies a transaction branch. Xid contains a format identifier, two length fields and a data field: format_id long gtrid_length octet bqual_length octet data format_id is an implementation specific format identifier the data field is a sequence of octets of at most 128 bytes containing the txn id and the branch id gtrid_length field indicates how many bytes of this form the transaction id bqual_length field indicates how many bytes of this form the branch id The sum of the two lengths must equal the length of the data field This class is part of the X-Open XA distributed transaction protocol support. It allows a channel to be selected for use with distributed transactions and the transactional boundaries for work on that channel to be demarcated. dtx-demarcation = C:SELECT S:SELECT-OK *demarcation demarcation = C:START S:START-OK C:END S:END-OK Access-tickets are propagated with XA association methods with the aim of restricting which users are allowed to control which transactions. The server MAY restrict transaction association to a particular identity. Enabling XA transaction support on a channel implies that the server MUST manage transactions demarcated by start-end blocks. That is to say that on this XA-enabled channel, work undergone within transactional blocks is performed on behalf a transaction branch whereas work performed outside of transactional blocks is NOT transactional. This method sets the channel to use distributed transactions. The client must use this method at least once on a channel before using XA demarcation operations. This method confirms to the client that the channel was successfully set to use distributed transactions. This method is called when messages should be produced and consumed on behalf a transaction branch identified by xid. If the method is invoked in an improper context (see class grammar) then the server MUST raise a channel exception with reply code 503 (command invalid) If neither join nor resume is specified is specified and the transaction branch specified by xid has previously been seen then the server MUST raise a channel exception with reply code 530 (not allowed). If join and resume are specified then the server MUST raise a channel exception with reply code 503 (command invalid) Access-ticket granted by the server for a specific realm. Specifies the xid of the transaction branch to be started. If Xid is already known by the broker then the server MUST raise a channel exception with reply code 530 (not allowed). Indicate that the start applies to joining a transaction previously seen. If the broker does not support join the server MUST raise a channel exception with reply code 540 (not implemented). Indicate that the start applies to resuming a suspended transaction branch specified. This method confirms to the client that the transaction branch is started or specify the error condition. xa-ok: Normal execution. xa-rbrollback: The broker marked the transaction branch rollback-only for an unspecified reason. This method is called when the work done on behalf a transaction branch finishes or needs to be suspended. If the method is invoked in an improper context (see class grammar) then the server MUST raise a channel exception with reply code 503 (command invalid) If suspend and fail are specified then the server MUST raise a channel exception with reply code 503 (command invalid) If an error occurs in ending the transaction branch then the server MUST raise a channel exception with reply code 541 (internal error) If neither fail nor suspend are specified then the portion of work has completed successfully Access-ticket granted by the server for a specific realm. Specifies the xid of the transaction branch to be ended. If Xid is unknown (the transaction branch has not been started or has already been ended) then the server MUST raise a channel exception with reply code 404 (not found). Indicates that the portion of work has failed otherwise the portion of work has completed successfully. If fail is specified then the transaction should be marked as rollback-only. Indicates that the transaction branch is temporarily suspended in an incomplete state. The transaction context is in a suspended state and must be resumed via the start method with resume specified. This method confirms to the client that the transaction branch is ended or specify the error condition. xa-ok: Normal execution. xa-rbrollback: The broker marked the transaction branch rollback-only for an unspecified reason. xa-rbtimeout: The work represented by this transaction branch took too long. This class is part of the X-Open XA distributed transaction protocol support. It allows the transaction manager to coordinate transaction outcomes. dtx-coordination = *coordination coordination = command / outcome / recovery command = C:SET-TIMEOUT S:SET-TIMEOUT-OK / C:GET-TIMEOUT S:GET-TIMEOUT-OK outcome = one-phase-commit / one-phase-rollback / two-phase-commit / two-phase-rollback one-phase-commit = C:COMMIT S:COMMIT-OK one-phase-rollback = C:ROLLBACK S:ROLLBACK-OK two-phase-commit = C:PREPARE S:PREPARE-OK C:COMMIT S:COMMIT-OK two-phase-rollback = C:PREPARE S:PREPARE-OK C:ROLLBACK S:ROLLBACK-OK recovery = C:RECOVER S:RECOVER-OK *recovery-outcome recovery-outcome = one-phase-commit / one-phase-rollback / C:FORGET S:FORGET-OK Access-tickets are propagated with XA demarcation methods with the aim of restricting which users are allowed to control which transactions. The server MAY restrict transaction coordination to a particular identity. This method commits the work associated with xid. Any produced messages are made available and any consumed messages are discarded. If an error occurs in committing the transaction branch then the server MUST raise a channel exception with reply code 541 (internal error) If the method is invoked in an improper context (see class grammar) then the server MUST raise a channel exception with reply code 503 (command invalid) Access-ticket granted by the server for a specific realm. Specifies the Xid of the transaction branch to be committed. If Xid is unknown (the transaction branch has not been started or has already been ended) then the server MUST raise a channel exception with reply code 404 (not found). If this method is called when Xid is still associated with a channel then the server MUST raise a channel exception with reply code 503 (command invalid) When set then one-phase commit optimization is used. This method confirms to the client that the transaction branch is committed or specify the error condition. xa-ok: Normal execution, xa-heurhaz: Due to some failure, the work done on behalf of the specified transaction branch may have been heuristically completed. xa-heurcom: Due to a heuristic decision, the work done on behalf of the specified transaction branch was committed. xa-heurrb: Due to a heuristic decision, the work done on behalf of the specified transaction branch was rolled back. xa-heurmix: Due to a heuristic decision, the work done on behalf of the specified transaction branch was partially committed and partially rolled back. xa-rbrollback: The broker marked the transaction branch rollback-only for an unspecified reason. xa-rbtimeout: The work represented by this transaction branch took too long. This method is called to forget about a heuristically completed transaction branch. If an error occurs in forgetting the transaction branch then the server MUST raise a channel exception with reply code 541 (internal error) If the method is invoked in an improper context (see class grammar) then the server MUST raise a channel exception with reply code 503 (command invalid) Access-ticket granted by the server for a specific realm. Specifies the xid of the transaction branch to be forgotten. If Xid is unknown (the transaction branch has not been started or has already been ended) then the server MUST raise a channel exception with reply code 404 (not found). If this method is called when Xid is still associated with a channel then the server MUST raise a channel exception with reply code 503 (command invalid) This method confirms to the client that the transaction branch is forgotten or specify the error condition. This method obtains the current transaction timeout value in seconds. If setTimeout was not used prior to invoking this method, the return value is the default timeout; otherwise, the value used in the previous setTimeout call is returned. Specifies the Xid of the transaction branch for getting the timeout. If Xid is unknown (the transaction branch has not been started or has already been ended) then the server MUST raise a channel exception with reply code 404 (not found). If an error occurs in setting the transaction timeout then the server MUST raise a channel exception with reply code 541 (internal error) This method returns the current transaction timeout value in seconds. The current transaction timeout value in seconds. This method prepares for commitment any message produced or consumed on behalf of xid. If an error occurs in preparing the transaction branch then the server MUST raise a channel exception with reply code 541 (internal error). The specified Xid may or may not have been prepared. If the method is invoked in an improper context (see class grammar) then the server MUST raise a channel exception with reply code 503 (command invalid) Once this method successfully returns it is guaranteed that the transaction branch may be either committed or rolled back regardless of failures. The knowledge of xid cannot be erased before commit or rollback complete the branch. Access-ticket granted by the server for a specific realm. Specifies the Xid of the transaction branch that can be prepared. If Xid is unknown (the transaction branch has not been started or has already been ended) then the server MUST raise a channel exception with reply code 404 (not found). If this method is called when Xid is still associated with a channel then the server MUST raise a channel exception with reply code 503 (command invalid) This method confirms to the client that the transaction branch is prepared or specify the error condition. xa-ok: Normal execution. xa-rdonly: The transaction branch was read-only and has been committed. xa-rbrollback: The broker marked the transaction branch rollback-only for an unspecified reason. xa-rbtimeout: The work represented by this transaction branch took too long. This method is called to obtain a list of transaction branches that are in a prepared or heuristically completed state. If an error occurs in recovering then the server MUST raise a channel exception with reply code 541 (internal error) If this endscan is used in conjunction with startscan then a single call starts and then ends a scan. If none of endscan and startscan are set then a recovery scan must already be started otherwise the server MUST raise a channel exception with reply code 503 (command invalid) Access-ticket granted by the server for a specific realm. Indicates that recovery scan should start. If a recovery scan is already open, the effect is as if the recovery scan were ended and then restarted. Indicates that the recovery scan should end after returning the Xids. Returns to the client a table of transaction Xids that are in a prepared or heuristically completed state. table containing transaction Xids that are in a prepared or heuristically completed state. This method rolls back the work associated with xid. Any produced messages are discarded and any consumed messages are re-enqueued. If an error occurs in rolling back the transaction branch then the server MUST raise a channel exception with reply code 541 (internal error) If the method is invoked in an improper context (see class grammar) then the server MUST raise a channel exception with reply code 503 (command invalid) Access-ticket granted by the server for a specific realm. Specifies the Xid of the transaction branch that can be rolled back. If Xid is unknown (the transaction branch has not been started or has already been ended) then the server MUST raise a channel exception with reply code 404 (not found). If this method is called when Xid is still associated with a channel then the server MUST raise a channel exception with reply code 503 (command invalid) This method confirms to the client that the transaction branch is rolled back or specify the error condition. xa-ok: Normal execution, xa-heurhaz: Due to some failure, the work done on behalf of the specified transaction branch may have been heuristically completed. xa-heurcom: Due to a heuristic decision, the work done on behalf of the specified transaction branch was committed. xa-heurrb: Due to a heuristic decision, the work done on behalf of the specified transaction branch was rolled back. xa-heurmix: Due to a heuristic decision, the work done on behalf of the specified transaction branch was partially committed and partially rolled back. xa-rbrollback: The broker marked the transaction branch rollback-only for an unspecified reason. xa-rbtimeout: The work represented by this transaction branch took too long. Sets the specified transaction branch timeout value in seconds. If an error occurs in setting the transaction timeout then the server MUST raise a channel exception with reply code 541 (internal error) Once set, this timeout value is effective until this method is reinvoked with a different value. A value of zero resets the timeout value to the default value. Access-ticket granted by the server for a specific realm. Specifies the Xid of the transaction branch for setting the timeout. If Xid is unknown (the transaction branch has not been started or has already been ended) then the server MUST raise a channel exception with reply code 404 (not found). The transaction timeout value in seconds. This method confirms that the timeout has been set. This is a utility class for querying and exchange about its bindings to queues. This method is used to request information on the bindings to a particular exchange. That information is conveyed in a query-ok method. A valid ticket should be provided. The name of the exchange for which binding information is being requested. If not specified explicitly the default exchange is implied. If populated then determine whether the given queue is bound to the exchange. If populated defines the routing key of the binding of interest, if not populated the request will ignore the routing key on bindings when searching for a match. If populated defines the arguments of the binding of interest if not populated the request will ignore the arguments on bindings when searching for a match This method is used in response to a query and conveys information on the bindings to a particular exchange. If set, the exchange for which information was requested is not known. If set, the queue specified is not known. A bit which if set indicates that no binding was found from the specified exchange to the specified queue. A bit which if set indicates that no binding was found from the specified exchange with the specified routing key. A bit which if set indicates that no binding was found from the specified exchange with the specified arguments. This method is used to request information on a particular exchange. That information is conveyed by an query-ok method. A valid ticket should be provided. The name of the exchange for which information is requested. If not specified explicitly the default exchange is implied. This method is used in response to a query request and conveys information on a particular exchange. The type of the exchange. Will be empty if the exchange is not found. The durability of the exchange, i.e. if set the exchange is durable. Will not be set if the exchange is not found. If set, the exchange for which information was requested is not known. A set of properties of the exchange whose syntax and semantics depends on the server implementation. Will be empty if the exchange is not found. This class allows for efficiently communicating information about completion of processing. The low-water mark for executed command-ids. All ids below this mark have been executed; above this mark, there are gaps containing unexecuted command ids (i.e. discontinuous). By definition, the first id above this mark (if it exists) is an unexecuted command-id. debian/control.in0000644000000000000000000000157712134274367011221 0ustar Source: amqp-specs Section: net Priority: optional Maintainer: Jonas Smedegaard Build-Depends: @cdbs@ Standards-Version: 3.9.4 Homepage: http://www.amqp.org/ Vcs-Git: git://git.debian.org:/git/collab-maint/amqp-specs Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/amqp-specs.git Package: amqp-specs Architecture: all Depends: ${misc:Depends} Description: specs for the Advanced Message Queuing Protocol (AMQP) AMQP is the Internet Protocol for Business Messaging . The Advanced Message Queuing Protocol (AMQP) is an open standard for passing business messages between applications or organizations. It connects systems, feeds business processes with the information they need and reliably transmits onward the instructions that achieve their goals. . This package provides current and legacy AMQP protocol specifications, needed by some implementations.