Sounds good. What would be the process of contribution to the project? I would imagine creating some small write-up on the planned changes, getting your agreement, submitting the patch, reviewing and committing?
Thanks, Michael -----Original Message----- From: Ben Pfaff [mailto:b...@nicira.com] Sent: Tuesday, November 11, 2014 4:38 PM To: Zayats, Michael Cc: discuss@openvswitch.org Subject: Re: [ovs-discuss] OVSDB list_dbs monitor/update On Wed, Nov 12, 2014 at 12:34:27AM +0000, Zayats, Michael wrote: > Not very frequent, may be a few times per day per participating device. > However, if DB is reasonably big and there are many monitoring clients, it > might get busy as clients reread all the data to find what changed since > monitors were dropped. > Can also make the troubleshooting more tricky as loss of connectivity doesn't > mean failure and there is no clear indication on the reason of disconnection. > > I understand that it might not be a priority for you - would it be possible > for us to contribute in order to enhance this aspect? That's fine with me. I suggest adding a JSON-RPC notification that a client can sign up for. Whenever the list of database changes, the server would send the new list to all of the clients that signed up for the notification (and continue to disconnect the other clients). _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
