[rabbitmq-discuss] queue selection based on a 'feature list'

[Laing, Michael]

Perhaps this approach will help. For example:

Using a key pattern of 'w.x.y.z':

A server supports: 'w.x.y.-'

A message needs: '-.x.y.-'

Bind with the complement of the server pattern: '*.*.*.z'

Publish with the complement of the message pattern: 'w.-.-.z'

If server capabilities overlap there is still a routing problem...

ml




On Wed, Oct 30, 2013 at 9:54 AM, Lawrence Freil
<lef at apago.com<javascript:_e({}, 'cvml', 'lef at apago.com');>
> wrote:

> Hello,
>
> I'm attempting to create a distributed message processing system in which
> messages posted requires a list of features and can only be posted to
> queues which have all the required features. In addition it needs to act as
> a direct exchange in that only one queue should receive a message. In
> looking over both the headers and topic exchanges it seems the wildcards
> are specified the wrong way around for this. For example, I have servers
> which can support optional features of w,x,y and z. When I publish a
> message it may require x and y. I don't care if the server it runs on
> supports w and z. So what I really need is the message to support the
> 'pattern'' and the queues to support the 'string'. Is there a way to
> accomplish this with the current exchanges?
>
> Thanks.
>
>
> --
> Lawrence Freil
>
> ______________________________**_________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.**rabbitmq.com <javascript:_e({}, 'cvml',
> 'rabbitmq-discuss at lists.rabbitmq.com');>
> https://lists.rabbitmq.com/**cgi-bin/mailman/listinfo/**rabbitmq-discuss<https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131030/42d28bdc/attachment.htm>