That should work just fine.<br clear="all"><br>Thanks,<br><br>- Jim<br><br>Jim Irrer <a href="mailto:irrer@umich.edu">irrer@umich.edu</a> (734) 647-4409<br>University of Michigan Hospital Radiation Oncology<br>519 W. William St. Ann Arbor, MI 48103<br>
<br><br><div class="gmail_quote">On Fri, Nov 18, 2011 at 2:16 PM, Julio Polo <span dir="ltr"><<a href="mailto:julio@hawaii.edu">julio@hawaii.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I'm wondering if it's feasible to set up a topic exchange and have the<br>
message routing key's first word be the person's identifier:<br>
<br>
<personNumericID>.<action>.<attribute><br>
<br>
This way, applications may subscribe only to messages for the few<br>
people they are interested in.<br>
<br>
Are there any performance issues if a word in a message routing key<br>
can have a very large range of values? Let's say 70,000 possible<br>
values. What if it grows to a million and beyond? Does it matter?<br>
<br>
I doubt we'd implement the above, but it's nice to know if it ever<br>
comes up. We're most likely to implement a message routing key like<br>
<deptCode>.<action>.<attribute> where <deptCode> can have about 1000<br>
possible values. I assume that should be no problem.<br>
<font color="#888888"><br>
Julio Polo<br>
University of Hawaii<br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</font></blockquote></div><br>