>On Mon, Feb 16, 2009 at 2:57 PM, Gordon Sim <[email protected]> wrote:
> The headers exchange only supports the limited mechanisms documented in
the 0-10 spec.

In that case, are there any ways to create Links between exchanges at the
server such that i can populate certain well known exchanges with messages
corresponding to some known conditions ?

Required condition = h1 = val1 and h2 = val2 and h3 in (val4, val5....valn)

So i create one exchange h1h2 such that all messages that match h1 = val1
and h2 = val2 gets send to this queue (via a link between two queues?) and
clients can subscribe using h3 = val4 or h3 = val5 .... syntax from this
exchange.

If there is some rich functionality available around this, i could use this
to simplify the client subscriptions and probably reduce the load on the
broker. I saw some broker administration examples on the amqp standard pdf
(section 9) that showed some similar scenarios. Are they available ?

Thanks
gs


On Mon, Feb 16, 2009 at 2:57 PM, Gordon Sim <[email protected]> wrote:

> GS.Chandra N wrote:
>
>> I'm trying to try out different ways of subscribing from header exchange.
>> Can i use SQL like syntax, as described in the standards draft?
>>
>
> The headers exchange only supports the limited mechanisms documented in the
> 0-10 spec. You specify the key-value pairs you want to match on and can then
> either choose to match them all (AND) or any of them (OR).
>
> The (non-standard) XML exchange allows Xquery selection based on headers,
> but currently I believe it requires the body to be in XML even if your query
> doesn't actually access the body.
>
> Selectors on subscribe is on the roadmap[1] but I think now unlikely to
> make it for the M5 feature freeze (hopefully it will be in the subsequent
> release however).
>
> [1] https://issues.apache.org/jira/browse/QPID-530
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:[email protected]
>
>

Reply via email to