Hi, When OVSDB server sends updates to an OVSDB client, the IDL changes idl_seqno. When idl_seqno changes, the client can rebrowse the IDL and look for changes.
Does OVSDB server guarantee that the updates always maintain referential integrity for row creation and row updates i.e. if the client browses the IDL it should never run into a situation where rowA in tableA points to a non-existent rowB in tableB because the update for rowA has arrived but update for rowB is still in flight. If the OVSDB server doesnt guarantee the above, what should the client do to make sure that IDL is in a consistent state before it is browsed. Thanks -- Saurabh (सौरभ)
_______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
