Hi,

>this can be done but using non-destructive consumers.

Cant subscriptions be created between multiple private queues -> public
queue that contain the messages everyone is interested in to create the same
effect? Or would that be too much of a load ?

I'm yet to start with the actual client api but the 1.0 draft design left me
with this impression.

On the same topic, how do message subscription get handled in a federated
environment.

Would clients connected anywhere in  the federated tree receieve messages
irrespect of where they originate ?
How do brokers in the federated tree come to know about subscriptions
created elsewhere in the heirarchy? Is this supported?

Thanks
gs

ps : Sorry if i might have asked too many questions if there is document i
can refer on that would do too.

On Thu, Feb 5, 2009 at 6:23 PM, Carl Trieloff <cctrieloff@redhat.com> wrote:

> chenta wrote:
>
>> Hi,
>> I am new to Qpid and I have a simple question.
>> Is it possible that there are more the one consumers subscribe to the same
>> queue but all receive the same message like broadcasting? or I have to use
>> pub-sub/fanout to do that? However, if I use fanout to do the "broadcast",
>> it means that every consumer have to own a unique queue, am I correct?
>>
>> Thanks,
>> Chenta
>>
>>
>
> this can be done but using non-destructive consumers. The messages can then
> be discarded via a
> variety of mechnism. Using the C++ broker the following options exist.
> - Using TTL to age and destroy the messages.
> - Size limiting the queue for discarding old messages via a size policy
> like ring.
> - etc
> On the Java broker,
> TTL would be the way to go.
>
> And ten of cause you can create an autodelete queue for each consumer. not
> really any cost
> in doing this also, allow destructive consumers.
>
> Carl.
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:users-subscribe@qpid.apache.org
>
>