I think that for the bulk write usecase it is more probable that the writer wants to disable the firing of (all) event handlers on its path and fire them at once at the end. So basically with the exclusion pattern there should be a predefined global excluded userdata that one can set on the ObservationManager in order to avoid all listeners. Otherwise the mechanism only works if the listener acts proactively on it (which might be more sane in the end :) ).
But this would rather be a thread scheduling issue than an observation issue. For this we'd better improve configurability of event generation/consumption and the associated thread pools. See also OAK-1368 for some ideas here.
Michael
