{and the first approach has the trouble of pairing the eventsObservablr to a given trigger call, if there is a parameter to it... most likely trigger would return some id, or subscription, which is a param to the events subscription, but in order to dumbly observe state, events subscription needs to happen in the ui constructor.. so its an ordering issue.. observable of observable is needed? and you have issues with clearing, i.e. somebody opens the events obs. for nonexisting id, etc)