X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=ovsdb%2FSPECS;h=d9c92dead942ae7aded4f09f7bd160689471c168;hb=b14c5fe9bd85b440d1727934c84d5f7fded051f7;hp=c926e2122b5b7059300f920254394a670d4c0428;hpb=a0bc29a541fc7dc6e20137d5558e2094d614e6ab;p=openvswitch diff --git a/ovsdb/SPECS b/ovsdb/SPECS index c926e212..d9c92dea 100644 --- a/ovsdb/SPECS +++ b/ovsdb/SPECS @@ -5,6 +5,19 @@ Basic Notation -------------- +OVSDB uses JSON, as defined by RFC 4627, for its schema format and its +wire protocol format. The JSON implementation in Open vSwitch has the +following limitations: + + - Null bytes (\u0000) are not allowed in strings. + + - Only UTF-8 encoding is supported. (RFC 4627 also mentions + UTF-16BE, UTF-16LE, and UTF-32.) + + - RFC 4627 says that names within a JSON object should be unique. + The Open vSwitch JSON parser discards all but the last value + for a name that is specified more than once. + The descriptions below use the following shorthand notations for JSON values. Additional notation is presented later. @@ -251,6 +264,8 @@ over HTTP, for these reasons: * The JSON-RPC specification for HTTP transport is incomplete. +We are using TCP port 6632 for the database JSON-RPC connection. + The database wire protocol consists of the following JSON-RPC methods: list_dbs @@ -423,8 +438,10 @@ Request object members: "params": [, , ] required "id": required - is an object that maps from a table name to a -. + is an object that maps from a table name to an +array of objects. For backward compatibility, a +single may be used instead of an array; it is +treated as a single-element array. Each is an object with the following members: @@ -445,15 +462,16 @@ Response object members: "id": same "id" as request This JSON-RPC request enables a client to replicate tables or subsets -of tables within database . Each specifies -a table to be replicated. The JSON-RPC response to the "monitor" -includes the initial contents of each table. Afterward, when changes -to those tables are committed, the changes are automatically sent to -the client using the "update" monitor notification. This monitoring -persists until the JSON-RPC session terminates or until the client -sends a "monitor_cancel" JSON-RPC request. +of tables within database . Each element of + specifies a table to be replicated. The JSON-RPC +response to the "monitor" includes the initial contents of each table, +unless disabled (see below). Afterward, when changes to those tables +are committed, the changes are automatically sent to the client using +the "update" monitor notification. This monitoring persists until the +JSON-RPC session terminates or until the client sends a +"monitor_cancel" JSON-RPC request. -Each describes how to monitor a table: +Each describes how to monitor columns in a table: The circumstances in which an "update" notification is sent for a row within the table are determined by : @@ -471,8 +489,13 @@ Each describes how to monitor a table: sent whenever when a row in the table is modified. The "columns" member specifies the columns whose values are - monitored. If "columns" is omitted, all columns in the table, - except for "_uuid", are monitored. + monitored. It must not contain duplicates. If "columns" is + omitted, all columns in the table, except for "_uuid", are + monitored. + +If there is more than one in an array of them, then +each in the array should specify both "columns" and +"select", and the "columns" must be non-overlapping sets. The "result" in the JSON-RPC response to the "monitor" request is a object (see below) that contains the contents of the