Note that the selector is sent by the client during table subscription; the selector is just a string, as it is handled by custom code it can be potentially anything.

Per each item/user combination the isSelectorAllowed method is called so you can avoid a user or item or combination from having selectors applied to their updates.

Then on each update the isSelected is called per each update/user

I don't have a workflow chart about selectors, please take a look at these javadoc: http://bit.ly/grxqRg