A "cheap" way to improve performance would be to run the selector against messages added to the queue, add references to these messages into a hashtable (key would be the selector, value would be the sorted message IDs). When reading using a selector, if it matches a pre-existing optimized selector exactly, then the references would be pulled from the selector hashtable.
One nice benefit is the selector is only evaluated once. A more sophisticated solution would include indexing each of the properties separately and using a tree. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831060#3831060 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831060 ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
