-
Notifications
You must be signed in to change notification settings - Fork 1
/
rows.proto
36 lines (29 loc) · 1.05 KB
/
rows.proto
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
// $Id: rows.proto,v 1.1 2008/12/16 10:04:05 bvandeenen Exp $
package avialogic.jdsclient.proto;
/* IMPORTANT. http://code.google.com/apis/protocolbuffers/docs/proto.html
As you can see, each field in the message definition has a unique numbered tag.
These tags are used to identify your fields in the message binary format, and
should not be changed once your message type is in use. Note that tags with
values in the range 1 through 15 take one byte to encode. Tags in the range 16
through 2047 take two bytes. So you should reserve the tags 1 through 15 for
very frequently occurring message elements. Remember to leave some room for
frequently occurring elements that might be added in the future.
*/
message PB_ROWUPD {
optional int32 channel =1;
optional int32 row =2;
optional int32 field =3;
optional string fieldvalue=4;
}
message PB_ROWINS {
required int32 channel = 1;
required int32 row = 2;
}
message PB_ROWDEL {
required int32 channel = 1;
required int32 row = 2;
}
message PB_ROWCLR {
required int32 channel = 1;
required int32 row = 2;
}