This maintains backward compatibility, but allows users to specifiy a map of functions
to handle subscription events, including 'nosub' and 'ready'. This allows monitoring for
changes to collections happening through mechanisms other than rpcs.
For added, changed, and removed, the ID of the relevant collection object is passed. In
the case of removed, the original object is passed as well.
The backwards compatible behaviour uses the generic callback for nosub and ready
events.
This maintains backward compatibility, but allows users to specifiy a map of functions to handle subscription events, including 'nosub' and 'ready'. This allows monitoring for changes to collections happening through mechanisms other than rpcs.
For added, changed, and removed, the ID of the relevant collection object is passed. In the case of removed, the original object is passed as well.
The backwards compatible behaviour uses the generic callback for nosub and ready events.