Ok, that answers my question. Thank you.
On Thu, Mar 8, 2018, 11:13 AM Ben Pfaff wrote:
> No. A JSON object can have any number of members.
>
> On Thu, Mar 08, 2018 at 11:06:21AM -0800, Anil Jangam wrote:
> > Thanks Ben for clarification. So it means one Monitor request can request
> > for only
No. A JSON object can have any number of members.
On Thu, Mar 08, 2018 at 11:06:21AM -0800, Anil Jangam wrote:
> Thanks Ben for clarification. So it means one Monitor request can request
> for only one Table monitoring, correct?
>
> On Thu, Mar 8, 2018 at 10:36 AM, Ben Pfaff wrote:
>
> > is a
Thanks Ben for clarification. So it means one Monitor request can request
for only one Table monitoring, correct?
On Thu, Mar 8, 2018 at 10:36 AM, Ben Pfaff wrote:
> is a JSON object. A JSON object maps from keys to
> values, so we only need one.
>
> Your specification for is wrong because it
is a JSON object. A JSON object maps from keys to
values, so we only need one.
Your specification for is wrong because it says that
it is a JSON array. It is not.
On Wed, Mar 07, 2018 at 09:32:06PM -0800, Anil Jangam wrote:
> Hello Ben,
>
> I have one more observation. I request you to pleas
Hello Ben,
I have one more observation. I request you to please read it carefully. If
we go by the current monitor method definition, there can be only
in one monitor RPC method. If it is expected to have only one
i.e. one table and an array of , then the current
specification is good.
o "meth
No. The "Reported-by:" tag is really just a kind of "thank-you".
Thanks again.
On Wed, Mar 07, 2018 at 02:50:32PM -0800, Anil Jangam wrote:
> Thanks you Ben! I saw the other patch email as well. Since it is says that
> "reported-by" me, do I have any further action item on me?
>
> /anil.
>
>
>
Thanks you Ben! I saw the other patch email as well. Since it is says that
"reported-by" me, do I have any further action item on me?
/anil.
On Wed, Mar 7, 2018 at 10:27 AM, Ben Pfaff wrote:
> Ah, OK, you're saying that there's a missing [] around the
> . This goes back to a change that we ma
Ah, OK, you're saying that there's a missing [] around the
. This goes back to a change that we made to the
ovsdb-server protocol a long time ago to allow multiple
objects instead of just a single one. ovsdb-server
still supports this form. You can see this documented in
Documentation/ref/ovsdb
Hello Ben,
The object maps the name of the table to be monitored
to an array of objects. Each is an
object with the following members:
"columns": [*]optional
"select": optional
As the maps the table name to be monitored to an array
of , my interpretatio
On Mon, Mar 05, 2018 at 10:03:13PM -0800, Anil Jangam wrote:
> Hi,
>
> The RFC7047 states below about the Monitor request.
>
> The request object has the
>
>following members:
>
>o "method": "monitor"
>
>o "params": [, , ]
>
>o "id":
>
>
> The parameter is used to match
10 matches
Mail list logo
