Hi Yes this module would be really useful for us if the VHost / exchange / routing key could be specified independently for the messages sent.
Maybe the routing key could be the message name in the raise event? e.g. E_PIKE_BLOCKED ? On 30 November 2011 12:20, Razvan Crainea <[email protected]>wrote: > Hi, Pete! > > Yes, indeed the RabbitMQ currently uses the same value for the exchange > name and routing key. Also only the '/' vhost can be used for the moment, > as it is hardcoded in the code. But this module is still under development > and any new ideas are welcome. > > Regards, > > -- > Răzvan Crainea > OpenSIPS Developer > > > On 11/30/2011 01:52 PM, Pete Kelly wrote: > > Hi > > I have a question about the RabbitMQ functionality. > > The documentation states that the 'exchange' will also be used as the > 'queue' used in RabbitMQ. > > In my experience you do not send messages directly to a queue in > RabbitMQ, you send message which contains > > - exchange name > - routing key > - message payload > > > RabbitMQ then uses the routing key to route the message to the correct > queue (or onward exchange). > > Can you tell me if the RabbitMQ implementation supports this, as it > sounds like it does not currently... it seems it uses the exchange as the > routing key as well as exchange? > > Pete > > > _______________________________________________ > Users mailing > [email protected]http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > >
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
