Hi Lance, let use in address string of the consumers just the exchange name, i.e.:
"amq.fanout" qpid client will detect from an answer of qpid broker that "amq.fanout" is an existing exchange and it will create an auxiliary, auto-delete & exclusive queue named like "amq.fanout_18efcccb-3abb-4db4-8ff0-7bb6a8fe0044" (exchange name, '_' and random UUID) and will bind it to the exchange. You can also specify routing key (that has no sense for fanout exchange, though) to be used in the binding, when using address string like "amq.direct/routingKey". Kind regards, Pavel Moravec ----- Original Message ----- > From: "Lance D." <lan...@gmail.com> > To: users@qpid.apache.org > Sent: Tuesday, December 18, 2012 4:09:00 AM > Subject: limit policy on bound temporary queues > > Hello, > > I'm trying to figure out a problem and I'm hoping to find the right > way to > make this happen. > > I've got a data producer that publishes to an fanout exchange. My > system > requires that under no circumstances can the producer get throttled > because > even if 1 user can't keep up, the other consumers need the data as > soon as > possible. My thought is that if I just force all of the consumers to > connect with a 'ring' limit policy, then I should be okay because > slow > consumers will just drop data on the floor. So I'd like to be able > to make > that the default policy. > > That said, I'm fairly certain that isn't possible, so I'd at least > like to > setup my clients with the correct settings. I've read through the > documentation, but I can't seem to figure out how to register to > receive > from an exchange, using a temporary (implicit) queue. > > Thanks in advance for the help. > -Lance > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
