2011/5/23 Gordon Sim <[email protected]>: > On 05/22/2011 04:59 AM, jun yang wrote: >> >> thanks for the answer. >> but the solution require the subscriber know too much of message detail. >> since my poor english,i am sorry that i don't express the meaning >> clearly, i do try again with the picture. >> in the picture,consumer-A22 just subscribe to exchange-A22,normally,it >> will comsue all message that send to exchange-A22,need not know what >> the subject of message is. > > So there is a 'fixed', i.e. relatively static, list of consumers and you > want to configure the set of messages these consumers get, i.e. the routing > rules, external to the consumer processes? > yes,it is the case.consumer-A22 always subcribe to exchange-A22,and some other program may dynamic create link to exchange-A22,or dynamic delete some link to exchange-A22.
> Why not use a queue for each consumer and bind that? I.e. create queue-A22 > etc, create appropriate bindings such that each consumer gets the messages > required then start the consumer. > yeap,thanks for the answer, it maybe is the practical solution for now,though i am thinking the link between exchange would be a more natruelly and intuitive approach, i bet all the function has almost implemented in qpid,just no api provide now. i would miss the function of qpid-route,you can bind queue to exchange,exchange to exchange,exchange to queue. the problem of queue is it's shared,so it is different from exchange, think about there will be some dynamic subscriber(consumer A22-1,A22-xx) of exchange-A22. > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > > --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
