Hi, In ODL, a given application's logic is mainly executed in context of data-tree-change notifications (or at the least, that is the most popular usage pattern).
And, typical consequential action for such notifications is to write back to one or more subtrees (using write/readwrite txns). Assuming an application has more than one change listeners on multiple subtrees, the execution-context of listeners would naturally be different across listeners. Such listeners, upon receiving notifications, again try to mutate one or more subtrees within same shard. Since the execution contexts are different for different notifications across listeners, single-writer principle would be violated. Are there any specific recommendations on how to coordinate events from disparate listeners and ensure that consequential updates to shard can still adhere to single-writer principle ? -- Regards Shirley
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
