Consumption mode
ActiveSpaces can proactively notify applications of changes to the tuples stored in a space. You can choose one of the consumption modes: Event Listener, Entry Browser, or Router.
When the consumption mode of a destination is event listener, the destination behaves like a subscriber in a publish-subscribe messaging system. When certain data changes or certain events occur, a callback function is invoked. You can choose the type of events to listen to: Put Event, Take Event, and Expire Event.
When the consumption mode is entry browser, the destination can monitor the space for data changes or certain events to occur, and can retrieve the tuple from the space using the browser type - Get or Take.
When the consumption mode is router, the destination feeds the events to only the specified listener. This way, the application benefits from having multiple listener processes running.