view release on metacpan or  search on metacpan

share/fixed_amqp0-9-1.xml  view on Meta::CPAN

          </doc>
          <doc type = "scenario">
            The client declares an exchange, binds a blank exchange
            name to it, and then unbinds a blank exchange name from
            it.
          </doc>
        </rule>
      </field>

      <field name = "source" domain = "exchange-name">
        <doc>Specifies the name of the source exchange to unbind.</doc>
        <rule name = "must-exist" on-failure = "not-found">
          <doc>
            The client MUST NOT attempt to unbind an exchange from an
            exchange that does not exist.
          </doc>
          <doc type = "scenario">
            The client attempts to unbind an exchange from a
            non-existent exchange.
          </doc>
        </rule>
        <rule name = "default-exchange">
          <doc>
            The server MUST accept a blank exchange name to mean the
            default exchange.
          </doc>
          <doc type = "scenario">
            The client declares an exchange, binds an exchange to a
            blank exchange name, and then unbinds an exchange from a
            black exchange name.
          </doc>
        </rule>
      </field>

      <field name = "routing-key" domain = "shortstr"
             label = "routing key of binding">
        <doc>Specifies the routing key of the binding to unbind.</doc>
      </field>

      <field name = "no-wait" domain = "no-wait"/>

      <field name = "arguments" domain = "table"
             label = "arguments of binding">
        <doc>Specifies the arguments of the binding to unbind.</doc>
      </field>
    </method>

    <method name = "unbind-ok" synchronous = "1" index = "51"
            label = "confirm unbind successful">
      <doc>This method confirms that the unbind was successful.</doc>
      <chassis name = "client" implement = "MUST"/>
    </method>

  </class>

  <!-- ==  QUEUE  ============================================================ -->

  <class name = "queue" handler = "channel" index = "50" label = "work with queues">
    <doc>
      Queues store and forward messages. Queues can be configured in the server or created at
      runtime. Queues must be attached to at least one exchange in order to receive messages
      from publishers.
    </doc>

    <doc type = "grammar">
      queue               = C:DECLARE  S:DECLARE-OK
                          / C:BIND     S:BIND-OK
                          / C:UNBIND   S:UNBIND-OK
                          / C:PURGE    S:PURGE-OK
                          / C:DELETE   S:DELETE-OK
    </doc>

    <chassis name = "server" implement = "MUST" />
    <chassis name = "client" implement = "MUST" />

    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->

    <method name = "declare" synchronous = "1" index = "10" label = "declare queue, create if needed">
      <doc>
        This method creates or checks a queue. When creating a new queue the client can
        specify various properties that control the durability of the queue and its
        contents, and the level of sharing for the queue.
      </doc>

      <rule name = "default-binding">
        <doc>
          The server MUST create a default binding for a newly-declared queue to the
          default exchange, which is an exchange of type 'direct' and use the queue
          name as the routing key.
        </doc>
        <doc type = "scenario">
          Client declares a new queue, and then without explicitly binding it to an
          exchange, attempts to send a message through the default exchange binding,
          i.e. publish a message to the empty exchange, with the queue name as routing
          key.
        </doc>
      </rule>

      <rule name = "minimum-queues">
        <doc>
          The server SHOULD support a minimum of 256 queues per virtual host and ideally,
          impose no limit except as defined by available resources.
        </doc>
        <doc type = "scenario">
          Client attempts to declare as many queues as it can until the server reports
          an error.  The resulting count must at least be 256.
        </doc>
      </rule>

      <chassis name = "server" implement = "MUST" />
      <response name = "declare-ok" />

      <!-- Deprecated: "ticket", must be zero -->
      <field name = "reserved-1" type = "short" reserved = "1" />

      <field name = "queue" domain = "queue-name">
        <rule name = "default-name">
          <doc>
            The queue name MAY be empty, in which case the server MUST create a new
            queue with a unique generated name and return this to the client in the
            Declare-Ok method.