Hi,
I have following suggestion on how to implement message selectors on MB
[image: Inline image 1]
- With cluster notification upon subscription we send selector
information as well.
- So each node knows all subscribers with their selector info
- When a message is published, when storing (or cloning and storing for
durable topic subscribers), we store only if selector matches
- This is possible if we expose selector logic of Qpid to andes core
using an interface.
- Then there will be no changes in delivery side. Even for durable topic
subscribers this will work.
WDYT? Please share your ideas.
Thanks
Hasitha
--
*Hasitha Abeykoon*
Senior Software Engineer; WSO2, Inc.; http://wso2.com
*cell:* *+94 719363063*
*blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com>
_______________________________________________
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
