[rabbitmq-discuss] New exchange type

[Kyle]

Attached is a revised version of the first patch with the changes below.
Rather than using a different exchange type, add "anycast" = 1 to the
arguments passed to exchangeDeclare. I've tested this with fanout and topic
exchanges with the RabbitMQ java library and py-amqplib from Barry Pederson.

Kyle

On Tue, Apr 22, 2008 at 1:16 AM, Matthias Radestock <matthias at lshift.net>
wrote:

>
> It occurred to me that rather than introducing a new exchange type one
> could place an indicator in the exchange arguments that turns any exchange
> from a multicast to an anycast exchange. That has two advantages:
>
> - we stay entirely within the defined protocol standard
>
> - the user can select the most appropriate matching logic with the
> exchange type, rather than being constrained to topic-based matching
>
> - use a flag in the process dictionary to indicate whether the random
> number generator has been seeded. Check/set that flag in your current code
> that invokes random:uniform. This has the same effect as the previous
> approach but is a less intrusive change since you don't need to touch any
> other modules.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20080423/c9b15828/attachment.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rabbit_exchange.erl.diff
Type: text/x-diff
Size: 1276 bytes
Desc: not available
Url : http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20080423/c9b15828/attachment.diff 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rabbit_exchange.erl
Type: application/octet-stream
Size: 14275 bytes
Desc: not available
Url : http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20080423/c9b15828/attachment.obj