On Thu, Jun 11, 2015 at 01:20:27PM -0700, Andy Zhou wrote:
> On Sat, Jun 6, 2015 at 2:23 PM, Ben Pfaff wrote:
> > On Mon, Jun 01, 2015 at 12:29:28AM -0700, Andy Zhou wrote:
> >> On Fri, May 29, 2015 at 1:05 PM, Ben Pfaff wrote:
> >> > On Thu, Apr 09, 2015 at 06:40:28PM -0700, Andy Zhou wrote:
> >
On Sat, Jun 6, 2015 at 2:23 PM, Ben Pfaff wrote:
> On Mon, Jun 01, 2015 at 12:29:28AM -0700, Andy Zhou wrote:
>> On Fri, May 29, 2015 at 1:05 PM, Ben Pfaff wrote:
>> > On Thu, Apr 09, 2015 at 06:40:28PM -0700, Andy Zhou wrote:
>> > The current implementation of ovsdb_monitor_commit() throws away
On Mon, Jun 01, 2015 at 12:29:28AM -0700, Andy Zhou wrote:
> On Fri, May 29, 2015 at 1:05 PM, Ben Pfaff wrote:
> > On Thu, Apr 09, 2015 at 06:40:28PM -0700, Andy Zhou wrote:
> > The current implementation of ovsdb_monitor_commit() throws away the
> > cache whenever there is any commit to the datab
On Fri, May 29, 2015 at 1:05 PM, Ben Pfaff wrote:
> On Thu, Apr 09, 2015 at 06:40:28PM -0700, Andy Zhou wrote:
>> Although multiple jsonrpc monitor can share the same ovsdb monitor, each
>> change still needs to transalted into json object from scratch. This
>> can be wastful is mutiple jsonrpc mo
On Thu, Apr 09, 2015 at 06:40:28PM -0700, Andy Zhou wrote:
> Although multiple jsonrpc monitor can share the same ovsdb monitor, each
> change still needs to transalted into json object from scratch. This
> can be wastful is mutiple jsonrpc monitors are interested in the
> same changes.
>
> Json c
