primary goal

• get away from the inevitable need of content changed events. In the new incarnation of the content app we try to stay away from the ContentChangedEvent since it is an error-prone and cumbersome way to communicate the changes. Instead we try to utilise the native datasource observation capabilities relief the app developer from having to send notifications manually.
• browser views should not have any imperative logic re: refreshing the views. Instead e.g. the table should use Vaadin DataProvider API and data providers should optionally subscribe to the backend events

possible solution

• JCR - use the wrapper around observation mechanism
  • do not want to have too many listeners at once. Maybe create a singleton pool of the listeners, which would broadcast the changes to the data providers?
  • non-JCR: depends on the capabilities of the backend
    • there could be no capabilities (like REST)
    • we could provide e.g. smth like localised CCE: specific action injects the specific DS observation and pushes the event
      additional complications
  • we have some relying on the CCE in other places. E.g. details sub-apps catch them and automatically close once it is received.
  • how do we leverage that situation?