view release on metacpan or  search on metacpan

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

          </doc>
          <doc type = "scenario">
            The client attempts to unbind a non-existent queue.
          </doc>
        </rule>
      </field>

      <field name = "exchange" domain = "exchange-name">
        <doc>The name of the exchange to unbind from.</doc>
        <rule name = "must-exist" on-failure = "not-found">
          <doc>
            The client MUST NOT attempt to unbind a queue from an exchange that
            does not exist.
          </doc>
          <doc type = "scenario">
            The client attempts to unbind a queue 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 a queue and binds it to a blank 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 = "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>

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

    <method name = "purge" synchronous = "1" index = "30" label = "purge a queue">
      <doc>
        This method removes all messages from a queue which are not awaiting
        acknowledgment.
      </doc>

      <rule name = "02">
        <doc>
          The server MUST NOT purge messages that have already been sent to a client
          but not yet acknowledged.
        </doc>
      </rule>

      <rule name = "03">
        <doc>
          The server MAY implement a purge queue or log that allows system administrators
          to recover accidentally-purged messages. The server SHOULD NOT keep purged
          messages in the same storage spaces as the live messages since the volumes of
          purged messages may get very large.
        </doc>
      </rule>

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

      <response name = "purge-ok" />

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

      <field name = "queue" domain = "queue-name">
        <doc>Specifies the name of the queue to purge.</doc>
        <rule name = "queue-known" on-failure = "not-found">
          <doc>
            The client MUST either specify a queue name or have previously declared a
            queue on the same channel
          </doc>
          <doc type = "scenario">
            The client opens a channel and attempts to purge an unnamed queue.
          </doc>
        </rule>
        <rule name = "must-exist" on-failure = "not-found">
          <doc>
            The client MUST NOT attempt to purge a queue that does not exist.
          </doc>
          <doc type = "scenario">
            The client attempts to purge a non-existent queue.
          </doc>
        </rule>
      </field>

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

    <method name = "purge-ok" synchronous = "1" index = "31" label = "confirms a queue purge">
      <doc>This method confirms the purge of a queue.</doc>

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

      <field name = "message-count" domain = "message-count">
        <doc>
          Reports the number of messages purged.
        </doc>
      </field>
    </method>

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

    <method name = "delete" synchronous = "1" index = "40" label = "delete a queue">
      <doc>
        This method deletes a queue. When a queue is deleted any pending messages are sent
        to a dead-letter queue if this is defined in the server configuration, and all
        consumers on the queue are cancelled.
      </doc>

      <rule name = "01">
        <doc>
          The server SHOULD use a dead-letter queue to hold messages that were pending on