grpc-tools 1.3.4 → 1.4.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/bin/x86-linux/google/protobuf/compiler/plugin.proto +4 -1
- data/bin/x86-linux/google/protobuf/descriptor.proto +6 -1
- data/bin/x86-linux/google/protobuf/duration.proto +14 -1
- data/bin/x86-linux/google/protobuf/timestamp.proto +25 -0
- data/bin/x86-linux/grpc_ruby_plugin +0 -0
- data/bin/x86-linux/protoc +0 -0
- data/bin/x86-macos/google/protobuf/compiler/plugin.proto +4 -1
- data/bin/x86-macos/google/protobuf/descriptor.proto +6 -1
- data/bin/x86-macos/google/protobuf/duration.proto +14 -1
- data/bin/x86-macos/google/protobuf/timestamp.proto +25 -0
- data/bin/x86-macos/grpc_ruby_plugin +0 -0
- data/bin/x86-macos/protoc +0 -0
- data/bin/x86-windows/google/protobuf/compiler/plugin.proto +4 -1
- data/bin/x86-windows/google/protobuf/descriptor.proto +6 -1
- data/bin/x86-windows/google/protobuf/duration.proto +14 -1
- data/bin/x86-windows/google/protobuf/timestamp.proto +25 -0
- data/bin/x86-windows/grpc_ruby_plugin.exe +0 -0
- data/bin/x86-windows/protoc.exe +0 -0
- data/bin/x86_64-linux/google/protobuf/compiler/plugin.proto +4 -1
- data/bin/x86_64-linux/google/protobuf/descriptor.proto +6 -1
- data/bin/x86_64-linux/google/protobuf/duration.proto +14 -1
- data/bin/x86_64-linux/google/protobuf/timestamp.proto +25 -0
- data/bin/x86_64-linux/grpc_ruby_plugin +0 -0
- data/bin/x86_64-linux/protoc +0 -0
- data/bin/x86_64-macos/google/protobuf/compiler/plugin.proto +4 -1
- data/bin/x86_64-macos/google/protobuf/descriptor.proto +6 -1
- data/bin/x86_64-macos/google/protobuf/duration.proto +14 -1
- data/bin/x86_64-macos/google/protobuf/timestamp.proto +25 -0
- data/bin/x86_64-macos/grpc_ruby_plugin +0 -0
- data/bin/x86_64-macos/protoc +0 -0
- data/bin/x86_64-windows/google/protobuf/compiler/plugin.proto +4 -1
- data/bin/x86_64-windows/google/protobuf/descriptor.proto +6 -1
- data/bin/x86_64-windows/google/protobuf/duration.proto +14 -1
- data/bin/x86_64-windows/google/protobuf/timestamp.proto +25 -0
- data/bin/x86_64-windows/grpc_ruby_plugin.exe +0 -0
- data/bin/x86_64-windows/protoc.exe +0 -0
- data/version.rb +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 7ceae4f357ccbaa0faf4e459dfb74a1b34dd597c
|
4
|
+
data.tar.gz: 006ba6f2e090f33cf01913720c274a2712b4d756
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: fe66a9c5516fa697da53d9044176cac98f387023074e39d5afab5a34bb6413e19cec1c1f598b613043a119d67d7845cd54347f493e2dadc88b834f099a9036d4
|
7
|
+
data.tar.gz: c151a4dc2562ab77ebe23e8ef4f15c24343990689da6618a18e73980807e75ff76bdf12dec9b41bcfa95b0a462496d46113f266cb91a4b9d7643791cce282c53
|
@@ -49,7 +49,7 @@ package google.protobuf.compiler;
|
|
49
49
|
option java_package = "com.google.protobuf.compiler";
|
50
50
|
option java_outer_classname = "PluginProtos";
|
51
51
|
|
52
|
-
option go_package = "plugin_go";
|
52
|
+
option go_package = "github.com/golang/protobuf/protoc-gen-go/plugin;plugin_go";
|
53
53
|
|
54
54
|
import "google/protobuf/descriptor.proto";
|
55
55
|
|
@@ -84,6 +84,9 @@ message CodeGeneratorRequest {
|
|
84
84
|
// the entire set into memory at once. However, as of this writing, this
|
85
85
|
// is not similarly optimized on protoc's end -- it will store all fields in
|
86
86
|
// memory at once before sending them to the plugin.
|
87
|
+
//
|
88
|
+
// Type names of fields and extensions in the FileDescriptorProto are always
|
89
|
+
// fully qualified.
|
87
90
|
repeated FileDescriptorProto proto_file = 15;
|
88
91
|
|
89
92
|
// The version number of protocol compiler.
|
@@ -376,6 +376,10 @@ message FileOptions {
|
|
376
376
|
// to prefix the types/symbols defined.
|
377
377
|
optional string swift_prefix = 39;
|
378
378
|
|
379
|
+
// Sets the php class prefix which is prepended to all php generated classes
|
380
|
+
// from this .proto. Default is empty.
|
381
|
+
optional string php_class_prefix = 40;
|
382
|
+
|
379
383
|
// The parser stores options it doesn't recognize here. See above.
|
380
384
|
repeated UninterpretedOption uninterpreted_option = 999;
|
381
385
|
|
@@ -441,7 +445,7 @@ message MessageOptions {
|
|
441
445
|
optional bool map_entry = 7;
|
442
446
|
|
443
447
|
reserved 8; // javalite_serializable
|
444
|
-
|
448
|
+
reserved 9; // javanano_as_lite
|
445
449
|
|
446
450
|
// The parser stores options it doesn't recognize here. See above.
|
447
451
|
repeated UninterpretedOption uninterpreted_option = 999;
|
@@ -561,6 +565,7 @@ message EnumOptions {
|
|
561
565
|
// is a formalization for deprecating enums.
|
562
566
|
optional bool deprecated = 3 [default=false];
|
563
567
|
|
568
|
+
reserved 5; // javanano_as_lite
|
564
569
|
|
565
570
|
// The parser stores options it doesn't recognize here. See above.
|
566
571
|
repeated UninterpretedOption uninterpreted_option = 999;
|
@@ -47,6 +47,8 @@ option objc_class_prefix = "GPB";
|
|
47
47
|
// two Timestamp values is a Duration and it can be added or subtracted
|
48
48
|
// from a Timestamp. Range is approximately +-10,000 years.
|
49
49
|
//
|
50
|
+
// # Examples
|
51
|
+
//
|
50
52
|
// Example 1: Compute Duration from two Timestamps in pseudo code.
|
51
53
|
//
|
52
54
|
// Timestamp start = ...;
|
@@ -87,11 +89,22 @@ option objc_class_prefix = "GPB";
|
|
87
89
|
// duration = Duration()
|
88
90
|
// duration.FromTimedelta(td)
|
89
91
|
//
|
92
|
+
// # JSON Mapping
|
93
|
+
//
|
94
|
+
// In JSON format, the Duration type is encoded as a string rather than an
|
95
|
+
// object, where the string ends in the suffix "s" (indicating seconds) and
|
96
|
+
// is preceded by the number of seconds, with nanoseconds expressed as
|
97
|
+
// fractional seconds. For example, 3 seconds with 0 nanoseconds should be
|
98
|
+
// encoded in JSON format as "3s", while 3 seconds and 1 nanosecond should
|
99
|
+
// be expressed in JSON format as "3.000000001s", and 3 seconds and 1
|
100
|
+
// microsecond should be expressed in JSON format as "3.000001s".
|
101
|
+
//
|
90
102
|
//
|
91
103
|
message Duration {
|
92
104
|
|
93
105
|
// Signed seconds of the span of time. Must be from -315,576,000,000
|
94
|
-
// to +315,576,000,000 inclusive.
|
106
|
+
// to +315,576,000,000 inclusive. Note: these bounds are computed from:
|
107
|
+
// 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
|
95
108
|
int64 seconds = 1;
|
96
109
|
|
97
110
|
// Signed fractions of a second at nanosecond resolution of the span
|
@@ -52,6 +52,8 @@ option objc_class_prefix = "GPB";
|
|
52
52
|
// and from RFC 3339 date strings.
|
53
53
|
// See [https://www.ietf.org/rfc/rfc3339.txt](https://www.ietf.org/rfc/rfc3339.txt).
|
54
54
|
//
|
55
|
+
// # Examples
|
56
|
+
//
|
55
57
|
// Example 1: Compute Timestamp from POSIX `time()`.
|
56
58
|
//
|
57
59
|
// Timestamp timestamp;
|
@@ -92,6 +94,29 @@ option objc_class_prefix = "GPB";
|
|
92
94
|
// timestamp = Timestamp()
|
93
95
|
// timestamp.GetCurrentTime()
|
94
96
|
//
|
97
|
+
// # JSON Mapping
|
98
|
+
//
|
99
|
+
// In JSON format, the Timestamp type is encoded as a string in the
|
100
|
+
// [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) format. That is, the
|
101
|
+
// format is "{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z"
|
102
|
+
// where {year} is always expressed using four digits while {month}, {day},
|
103
|
+
// {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional
|
104
|
+
// seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution),
|
105
|
+
// are optional. The "Z" suffix indicates the timezone ("UTC"); the timezone
|
106
|
+
// is required, though only UTC (as indicated by "Z") is presently supported.
|
107
|
+
//
|
108
|
+
// For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past
|
109
|
+
// 01:30 UTC on January 15, 2017.
|
110
|
+
//
|
111
|
+
// In JavaScript, one can convert a Date object to this format using the
|
112
|
+
// standard [toISOString()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString]
|
113
|
+
// method. In Python, a standard `datetime.datetime` object can be converted
|
114
|
+
// to this format using [`strftime`](https://docs.python.org/2/library/time.html#time.strftime)
|
115
|
+
// with the time format spec '%Y-%m-%dT%H:%M:%S.%fZ'. Likewise, in Java, one
|
116
|
+
// can use the Joda Time's [`ISODateTimeFormat.dateTime()`](
|
117
|
+
// http://joda-time.sourceforge.net/apidocs/org/joda/time/format/ISODateTimeFormat.html#dateTime())
|
118
|
+
// to obtain a formatter capable of generating timestamps in this format.
|
119
|
+
//
|
95
120
|
//
|
96
121
|
message Timestamp {
|
97
122
|
|
Binary file
|
data/bin/x86-linux/protoc
CHANGED
Binary file
|
@@ -49,7 +49,7 @@ package google.protobuf.compiler;
|
|
49
49
|
option java_package = "com.google.protobuf.compiler";
|
50
50
|
option java_outer_classname = "PluginProtos";
|
51
51
|
|
52
|
-
option go_package = "plugin_go";
|
52
|
+
option go_package = "github.com/golang/protobuf/protoc-gen-go/plugin;plugin_go";
|
53
53
|
|
54
54
|
import "google/protobuf/descriptor.proto";
|
55
55
|
|
@@ -84,6 +84,9 @@ message CodeGeneratorRequest {
|
|
84
84
|
// the entire set into memory at once. However, as of this writing, this
|
85
85
|
// is not similarly optimized on protoc's end -- it will store all fields in
|
86
86
|
// memory at once before sending them to the plugin.
|
87
|
+
//
|
88
|
+
// Type names of fields and extensions in the FileDescriptorProto are always
|
89
|
+
// fully qualified.
|
87
90
|
repeated FileDescriptorProto proto_file = 15;
|
88
91
|
|
89
92
|
// The version number of protocol compiler.
|
@@ -376,6 +376,10 @@ message FileOptions {
|
|
376
376
|
// to prefix the types/symbols defined.
|
377
377
|
optional string swift_prefix = 39;
|
378
378
|
|
379
|
+
// Sets the php class prefix which is prepended to all php generated classes
|
380
|
+
// from this .proto. Default is empty.
|
381
|
+
optional string php_class_prefix = 40;
|
382
|
+
|
379
383
|
// The parser stores options it doesn't recognize here. See above.
|
380
384
|
repeated UninterpretedOption uninterpreted_option = 999;
|
381
385
|
|
@@ -441,7 +445,7 @@ message MessageOptions {
|
|
441
445
|
optional bool map_entry = 7;
|
442
446
|
|
443
447
|
reserved 8; // javalite_serializable
|
444
|
-
|
448
|
+
reserved 9; // javanano_as_lite
|
445
449
|
|
446
450
|
// The parser stores options it doesn't recognize here. See above.
|
447
451
|
repeated UninterpretedOption uninterpreted_option = 999;
|
@@ -561,6 +565,7 @@ message EnumOptions {
|
|
561
565
|
// is a formalization for deprecating enums.
|
562
566
|
optional bool deprecated = 3 [default=false];
|
563
567
|
|
568
|
+
reserved 5; // javanano_as_lite
|
564
569
|
|
565
570
|
// The parser stores options it doesn't recognize here. See above.
|
566
571
|
repeated UninterpretedOption uninterpreted_option = 999;
|
@@ -47,6 +47,8 @@ option objc_class_prefix = "GPB";
|
|
47
47
|
// two Timestamp values is a Duration and it can be added or subtracted
|
48
48
|
// from a Timestamp. Range is approximately +-10,000 years.
|
49
49
|
//
|
50
|
+
// # Examples
|
51
|
+
//
|
50
52
|
// Example 1: Compute Duration from two Timestamps in pseudo code.
|
51
53
|
//
|
52
54
|
// Timestamp start = ...;
|
@@ -87,11 +89,22 @@ option objc_class_prefix = "GPB";
|
|
87
89
|
// duration = Duration()
|
88
90
|
// duration.FromTimedelta(td)
|
89
91
|
//
|
92
|
+
// # JSON Mapping
|
93
|
+
//
|
94
|
+
// In JSON format, the Duration type is encoded as a string rather than an
|
95
|
+
// object, where the string ends in the suffix "s" (indicating seconds) and
|
96
|
+
// is preceded by the number of seconds, with nanoseconds expressed as
|
97
|
+
// fractional seconds. For example, 3 seconds with 0 nanoseconds should be
|
98
|
+
// encoded in JSON format as "3s", while 3 seconds and 1 nanosecond should
|
99
|
+
// be expressed in JSON format as "3.000000001s", and 3 seconds and 1
|
100
|
+
// microsecond should be expressed in JSON format as "3.000001s".
|
101
|
+
//
|
90
102
|
//
|
91
103
|
message Duration {
|
92
104
|
|
93
105
|
// Signed seconds of the span of time. Must be from -315,576,000,000
|
94
|
-
// to +315,576,000,000 inclusive.
|
106
|
+
// to +315,576,000,000 inclusive. Note: these bounds are computed from:
|
107
|
+
// 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
|
95
108
|
int64 seconds = 1;
|
96
109
|
|
97
110
|
// Signed fractions of a second at nanosecond resolution of the span
|
@@ -52,6 +52,8 @@ option objc_class_prefix = "GPB";
|
|
52
52
|
// and from RFC 3339 date strings.
|
53
53
|
// See [https://www.ietf.org/rfc/rfc3339.txt](https://www.ietf.org/rfc/rfc3339.txt).
|
54
54
|
//
|
55
|
+
// # Examples
|
56
|
+
//
|
55
57
|
// Example 1: Compute Timestamp from POSIX `time()`.
|
56
58
|
//
|
57
59
|
// Timestamp timestamp;
|
@@ -92,6 +94,29 @@ option objc_class_prefix = "GPB";
|
|
92
94
|
// timestamp = Timestamp()
|
93
95
|
// timestamp.GetCurrentTime()
|
94
96
|
//
|
97
|
+
// # JSON Mapping
|
98
|
+
//
|
99
|
+
// In JSON format, the Timestamp type is encoded as a string in the
|
100
|
+
// [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) format. That is, the
|
101
|
+
// format is "{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z"
|
102
|
+
// where {year} is always expressed using four digits while {month}, {day},
|
103
|
+
// {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional
|
104
|
+
// seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution),
|
105
|
+
// are optional. The "Z" suffix indicates the timezone ("UTC"); the timezone
|
106
|
+
// is required, though only UTC (as indicated by "Z") is presently supported.
|
107
|
+
//
|
108
|
+
// For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past
|
109
|
+
// 01:30 UTC on January 15, 2017.
|
110
|
+
//
|
111
|
+
// In JavaScript, one can convert a Date object to this format using the
|
112
|
+
// standard [toISOString()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString]
|
113
|
+
// method. In Python, a standard `datetime.datetime` object can be converted
|
114
|
+
// to this format using [`strftime`](https://docs.python.org/2/library/time.html#time.strftime)
|
115
|
+
// with the time format spec '%Y-%m-%dT%H:%M:%S.%fZ'. Likewise, in Java, one
|
116
|
+
// can use the Joda Time's [`ISODateTimeFormat.dateTime()`](
|
117
|
+
// http://joda-time.sourceforge.net/apidocs/org/joda/time/format/ISODateTimeFormat.html#dateTime())
|
118
|
+
// to obtain a formatter capable of generating timestamps in this format.
|
119
|
+
//
|
95
120
|
//
|
96
121
|
message Timestamp {
|
97
122
|
|
Binary file
|
data/bin/x86-macos/protoc
CHANGED
Binary file
|
@@ -49,7 +49,7 @@ package google.protobuf.compiler;
|
|
49
49
|
option java_package = "com.google.protobuf.compiler";
|
50
50
|
option java_outer_classname = "PluginProtos";
|
51
51
|
|
52
|
-
option go_package = "plugin_go";
|
52
|
+
option go_package = "github.com/golang/protobuf/protoc-gen-go/plugin;plugin_go";
|
53
53
|
|
54
54
|
import "google/protobuf/descriptor.proto";
|
55
55
|
|
@@ -84,6 +84,9 @@ message CodeGeneratorRequest {
|
|
84
84
|
// the entire set into memory at once. However, as of this writing, this
|
85
85
|
// is not similarly optimized on protoc's end -- it will store all fields in
|
86
86
|
// memory at once before sending them to the plugin.
|
87
|
+
//
|
88
|
+
// Type names of fields and extensions in the FileDescriptorProto are always
|
89
|
+
// fully qualified.
|
87
90
|
repeated FileDescriptorProto proto_file = 15;
|
88
91
|
|
89
92
|
// The version number of protocol compiler.
|
@@ -376,6 +376,10 @@ message FileOptions {
|
|
376
376
|
// to prefix the types/symbols defined.
|
377
377
|
optional string swift_prefix = 39;
|
378
378
|
|
379
|
+
// Sets the php class prefix which is prepended to all php generated classes
|
380
|
+
// from this .proto. Default is empty.
|
381
|
+
optional string php_class_prefix = 40;
|
382
|
+
|
379
383
|
// The parser stores options it doesn't recognize here. See above.
|
380
384
|
repeated UninterpretedOption uninterpreted_option = 999;
|
381
385
|
|
@@ -441,7 +445,7 @@ message MessageOptions {
|
|
441
445
|
optional bool map_entry = 7;
|
442
446
|
|
443
447
|
reserved 8; // javalite_serializable
|
444
|
-
|
448
|
+
reserved 9; // javanano_as_lite
|
445
449
|
|
446
450
|
// The parser stores options it doesn't recognize here. See above.
|
447
451
|
repeated UninterpretedOption uninterpreted_option = 999;
|
@@ -561,6 +565,7 @@ message EnumOptions {
|
|
561
565
|
// is a formalization for deprecating enums.
|
562
566
|
optional bool deprecated = 3 [default=false];
|
563
567
|
|
568
|
+
reserved 5; // javanano_as_lite
|
564
569
|
|
565
570
|
// The parser stores options it doesn't recognize here. See above.
|
566
571
|
repeated UninterpretedOption uninterpreted_option = 999;
|
@@ -47,6 +47,8 @@ option objc_class_prefix = "GPB";
|
|
47
47
|
// two Timestamp values is a Duration and it can be added or subtracted
|
48
48
|
// from a Timestamp. Range is approximately +-10,000 years.
|
49
49
|
//
|
50
|
+
// # Examples
|
51
|
+
//
|
50
52
|
// Example 1: Compute Duration from two Timestamps in pseudo code.
|
51
53
|
//
|
52
54
|
// Timestamp start = ...;
|
@@ -87,11 +89,22 @@ option objc_class_prefix = "GPB";
|
|
87
89
|
// duration = Duration()
|
88
90
|
// duration.FromTimedelta(td)
|
89
91
|
//
|
92
|
+
// # JSON Mapping
|
93
|
+
//
|
94
|
+
// In JSON format, the Duration type is encoded as a string rather than an
|
95
|
+
// object, where the string ends in the suffix "s" (indicating seconds) and
|
96
|
+
// is preceded by the number of seconds, with nanoseconds expressed as
|
97
|
+
// fractional seconds. For example, 3 seconds with 0 nanoseconds should be
|
98
|
+
// encoded in JSON format as "3s", while 3 seconds and 1 nanosecond should
|
99
|
+
// be expressed in JSON format as "3.000000001s", and 3 seconds and 1
|
100
|
+
// microsecond should be expressed in JSON format as "3.000001s".
|
101
|
+
//
|
90
102
|
//
|
91
103
|
message Duration {
|
92
104
|
|
93
105
|
// Signed seconds of the span of time. Must be from -315,576,000,000
|
94
|
-
// to +315,576,000,000 inclusive.
|
106
|
+
// to +315,576,000,000 inclusive. Note: these bounds are computed from:
|
107
|
+
// 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
|
95
108
|
int64 seconds = 1;
|
96
109
|
|
97
110
|
// Signed fractions of a second at nanosecond resolution of the span
|
@@ -52,6 +52,8 @@ option objc_class_prefix = "GPB";
|
|
52
52
|
// and from RFC 3339 date strings.
|
53
53
|
// See [https://www.ietf.org/rfc/rfc3339.txt](https://www.ietf.org/rfc/rfc3339.txt).
|
54
54
|
//
|
55
|
+
// # Examples
|
56
|
+
//
|
55
57
|
// Example 1: Compute Timestamp from POSIX `time()`.
|
56
58
|
//
|
57
59
|
// Timestamp timestamp;
|
@@ -92,6 +94,29 @@ option objc_class_prefix = "GPB";
|
|
92
94
|
// timestamp = Timestamp()
|
93
95
|
// timestamp.GetCurrentTime()
|
94
96
|
//
|
97
|
+
// # JSON Mapping
|
98
|
+
//
|
99
|
+
// In JSON format, the Timestamp type is encoded as a string in the
|
100
|
+
// [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) format. That is, the
|
101
|
+
// format is "{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z"
|
102
|
+
// where {year} is always expressed using four digits while {month}, {day},
|
103
|
+
// {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional
|
104
|
+
// seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution),
|
105
|
+
// are optional. The "Z" suffix indicates the timezone ("UTC"); the timezone
|
106
|
+
// is required, though only UTC (as indicated by "Z") is presently supported.
|
107
|
+
//
|
108
|
+
// For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past
|
109
|
+
// 01:30 UTC on January 15, 2017.
|
110
|
+
//
|
111
|
+
// In JavaScript, one can convert a Date object to this format using the
|
112
|
+
// standard [toISOString()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString]
|
113
|
+
// method. In Python, a standard `datetime.datetime` object can be converted
|
114
|
+
// to this format using [`strftime`](https://docs.python.org/2/library/time.html#time.strftime)
|
115
|
+
// with the time format spec '%Y-%m-%dT%H:%M:%S.%fZ'. Likewise, in Java, one
|
116
|
+
// can use the Joda Time's [`ISODateTimeFormat.dateTime()`](
|
117
|
+
// http://joda-time.sourceforge.net/apidocs/org/joda/time/format/ISODateTimeFormat.html#dateTime())
|
118
|
+
// to obtain a formatter capable of generating timestamps in this format.
|
119
|
+
//
|
95
120
|
//
|
96
121
|
message Timestamp {
|
97
122
|
|
Binary file
|
data/bin/x86-windows/protoc.exe
CHANGED
Binary file
|
@@ -49,7 +49,7 @@ package google.protobuf.compiler;
|
|
49
49
|
option java_package = "com.google.protobuf.compiler";
|
50
50
|
option java_outer_classname = "PluginProtos";
|
51
51
|
|
52
|
-
option go_package = "plugin_go";
|
52
|
+
option go_package = "github.com/golang/protobuf/protoc-gen-go/plugin;plugin_go";
|
53
53
|
|
54
54
|
import "google/protobuf/descriptor.proto";
|
55
55
|
|
@@ -84,6 +84,9 @@ message CodeGeneratorRequest {
|
|
84
84
|
// the entire set into memory at once. However, as of this writing, this
|
85
85
|
// is not similarly optimized on protoc's end -- it will store all fields in
|
86
86
|
// memory at once before sending them to the plugin.
|
87
|
+
//
|
88
|
+
// Type names of fields and extensions in the FileDescriptorProto are always
|
89
|
+
// fully qualified.
|
87
90
|
repeated FileDescriptorProto proto_file = 15;
|
88
91
|
|
89
92
|
// The version number of protocol compiler.
|
@@ -376,6 +376,10 @@ message FileOptions {
|
|
376
376
|
// to prefix the types/symbols defined.
|
377
377
|
optional string swift_prefix = 39;
|
378
378
|
|
379
|
+
// Sets the php class prefix which is prepended to all php generated classes
|
380
|
+
// from this .proto. Default is empty.
|
381
|
+
optional string php_class_prefix = 40;
|
382
|
+
|
379
383
|
// The parser stores options it doesn't recognize here. See above.
|
380
384
|
repeated UninterpretedOption uninterpreted_option = 999;
|
381
385
|
|
@@ -441,7 +445,7 @@ message MessageOptions {
|
|
441
445
|
optional bool map_entry = 7;
|
442
446
|
|
443
447
|
reserved 8; // javalite_serializable
|
444
|
-
|
448
|
+
reserved 9; // javanano_as_lite
|
445
449
|
|
446
450
|
// The parser stores options it doesn't recognize here. See above.
|
447
451
|
repeated UninterpretedOption uninterpreted_option = 999;
|
@@ -561,6 +565,7 @@ message EnumOptions {
|
|
561
565
|
// is a formalization for deprecating enums.
|
562
566
|
optional bool deprecated = 3 [default=false];
|
563
567
|
|
568
|
+
reserved 5; // javanano_as_lite
|
564
569
|
|
565
570
|
// The parser stores options it doesn't recognize here. See above.
|
566
571
|
repeated UninterpretedOption uninterpreted_option = 999;
|
@@ -47,6 +47,8 @@ option objc_class_prefix = "GPB";
|
|
47
47
|
// two Timestamp values is a Duration and it can be added or subtracted
|
48
48
|
// from a Timestamp. Range is approximately +-10,000 years.
|
49
49
|
//
|
50
|
+
// # Examples
|
51
|
+
//
|
50
52
|
// Example 1: Compute Duration from two Timestamps in pseudo code.
|
51
53
|
//
|
52
54
|
// Timestamp start = ...;
|
@@ -87,11 +89,22 @@ option objc_class_prefix = "GPB";
|
|
87
89
|
// duration = Duration()
|
88
90
|
// duration.FromTimedelta(td)
|
89
91
|
//
|
92
|
+
// # JSON Mapping
|
93
|
+
//
|
94
|
+
// In JSON format, the Duration type is encoded as a string rather than an
|
95
|
+
// object, where the string ends in the suffix "s" (indicating seconds) and
|
96
|
+
// is preceded by the number of seconds, with nanoseconds expressed as
|
97
|
+
// fractional seconds. For example, 3 seconds with 0 nanoseconds should be
|
98
|
+
// encoded in JSON format as "3s", while 3 seconds and 1 nanosecond should
|
99
|
+
// be expressed in JSON format as "3.000000001s", and 3 seconds and 1
|
100
|
+
// microsecond should be expressed in JSON format as "3.000001s".
|
101
|
+
//
|
90
102
|
//
|
91
103
|
message Duration {
|
92
104
|
|
93
105
|
// Signed seconds of the span of time. Must be from -315,576,000,000
|
94
|
-
// to +315,576,000,000 inclusive.
|
106
|
+
// to +315,576,000,000 inclusive. Note: these bounds are computed from:
|
107
|
+
// 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
|
95
108
|
int64 seconds = 1;
|
96
109
|
|
97
110
|
// Signed fractions of a second at nanosecond resolution of the span
|
@@ -52,6 +52,8 @@ option objc_class_prefix = "GPB";
|
|
52
52
|
// and from RFC 3339 date strings.
|
53
53
|
// See [https://www.ietf.org/rfc/rfc3339.txt](https://www.ietf.org/rfc/rfc3339.txt).
|
54
54
|
//
|
55
|
+
// # Examples
|
56
|
+
//
|
55
57
|
// Example 1: Compute Timestamp from POSIX `time()`.
|
56
58
|
//
|
57
59
|
// Timestamp timestamp;
|
@@ -92,6 +94,29 @@ option objc_class_prefix = "GPB";
|
|
92
94
|
// timestamp = Timestamp()
|
93
95
|
// timestamp.GetCurrentTime()
|
94
96
|
//
|
97
|
+
// # JSON Mapping
|
98
|
+
//
|
99
|
+
// In JSON format, the Timestamp type is encoded as a string in the
|
100
|
+
// [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) format. That is, the
|
101
|
+
// format is "{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z"
|
102
|
+
// where {year} is always expressed using four digits while {month}, {day},
|
103
|
+
// {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional
|
104
|
+
// seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution),
|
105
|
+
// are optional. The "Z" suffix indicates the timezone ("UTC"); the timezone
|
106
|
+
// is required, though only UTC (as indicated by "Z") is presently supported.
|
107
|
+
//
|
108
|
+
// For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past
|
109
|
+
// 01:30 UTC on January 15, 2017.
|
110
|
+
//
|
111
|
+
// In JavaScript, one can convert a Date object to this format using the
|
112
|
+
// standard [toISOString()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString]
|
113
|
+
// method. In Python, a standard `datetime.datetime` object can be converted
|
114
|
+
// to this format using [`strftime`](https://docs.python.org/2/library/time.html#time.strftime)
|
115
|
+
// with the time format spec '%Y-%m-%dT%H:%M:%S.%fZ'. Likewise, in Java, one
|
116
|
+
// can use the Joda Time's [`ISODateTimeFormat.dateTime()`](
|
117
|
+
// http://joda-time.sourceforge.net/apidocs/org/joda/time/format/ISODateTimeFormat.html#dateTime())
|
118
|
+
// to obtain a formatter capable of generating timestamps in this format.
|
119
|
+
//
|
95
120
|
//
|
96
121
|
message Timestamp {
|
97
122
|
|
Binary file
|
data/bin/x86_64-linux/protoc
CHANGED
Binary file
|
@@ -49,7 +49,7 @@ package google.protobuf.compiler;
|
|
49
49
|
option java_package = "com.google.protobuf.compiler";
|
50
50
|
option java_outer_classname = "PluginProtos";
|
51
51
|
|
52
|
-
option go_package = "plugin_go";
|
52
|
+
option go_package = "github.com/golang/protobuf/protoc-gen-go/plugin;plugin_go";
|
53
53
|
|
54
54
|
import "google/protobuf/descriptor.proto";
|
55
55
|
|
@@ -84,6 +84,9 @@ message CodeGeneratorRequest {
|
|
84
84
|
// the entire set into memory at once. However, as of this writing, this
|
85
85
|
// is not similarly optimized on protoc's end -- it will store all fields in
|
86
86
|
// memory at once before sending them to the plugin.
|
87
|
+
//
|
88
|
+
// Type names of fields and extensions in the FileDescriptorProto are always
|
89
|
+
// fully qualified.
|
87
90
|
repeated FileDescriptorProto proto_file = 15;
|
88
91
|
|
89
92
|
// The version number of protocol compiler.
|
@@ -376,6 +376,10 @@ message FileOptions {
|
|
376
376
|
// to prefix the types/symbols defined.
|
377
377
|
optional string swift_prefix = 39;
|
378
378
|
|
379
|
+
// Sets the php class prefix which is prepended to all php generated classes
|
380
|
+
// from this .proto. Default is empty.
|
381
|
+
optional string php_class_prefix = 40;
|
382
|
+
|
379
383
|
// The parser stores options it doesn't recognize here. See above.
|
380
384
|
repeated UninterpretedOption uninterpreted_option = 999;
|
381
385
|
|
@@ -441,7 +445,7 @@ message MessageOptions {
|
|
441
445
|
optional bool map_entry = 7;
|
442
446
|
|
443
447
|
reserved 8; // javalite_serializable
|
444
|
-
|
448
|
+
reserved 9; // javanano_as_lite
|
445
449
|
|
446
450
|
// The parser stores options it doesn't recognize here. See above.
|
447
451
|
repeated UninterpretedOption uninterpreted_option = 999;
|
@@ -561,6 +565,7 @@ message EnumOptions {
|
|
561
565
|
// is a formalization for deprecating enums.
|
562
566
|
optional bool deprecated = 3 [default=false];
|
563
567
|
|
568
|
+
reserved 5; // javanano_as_lite
|
564
569
|
|
565
570
|
// The parser stores options it doesn't recognize here. See above.
|
566
571
|
repeated UninterpretedOption uninterpreted_option = 999;
|
@@ -47,6 +47,8 @@ option objc_class_prefix = "GPB";
|
|
47
47
|
// two Timestamp values is a Duration and it can be added or subtracted
|
48
48
|
// from a Timestamp. Range is approximately +-10,000 years.
|
49
49
|
//
|
50
|
+
// # Examples
|
51
|
+
//
|
50
52
|
// Example 1: Compute Duration from two Timestamps in pseudo code.
|
51
53
|
//
|
52
54
|
// Timestamp start = ...;
|
@@ -87,11 +89,22 @@ option objc_class_prefix = "GPB";
|
|
87
89
|
// duration = Duration()
|
88
90
|
// duration.FromTimedelta(td)
|
89
91
|
//
|
92
|
+
// # JSON Mapping
|
93
|
+
//
|
94
|
+
// In JSON format, the Duration type is encoded as a string rather than an
|
95
|
+
// object, where the string ends in the suffix "s" (indicating seconds) and
|
96
|
+
// is preceded by the number of seconds, with nanoseconds expressed as
|
97
|
+
// fractional seconds. For example, 3 seconds with 0 nanoseconds should be
|
98
|
+
// encoded in JSON format as "3s", while 3 seconds and 1 nanosecond should
|
99
|
+
// be expressed in JSON format as "3.000000001s", and 3 seconds and 1
|
100
|
+
// microsecond should be expressed in JSON format as "3.000001s".
|
101
|
+
//
|
90
102
|
//
|
91
103
|
message Duration {
|
92
104
|
|
93
105
|
// Signed seconds of the span of time. Must be from -315,576,000,000
|
94
|
-
// to +315,576,000,000 inclusive.
|
106
|
+
// to +315,576,000,000 inclusive. Note: these bounds are computed from:
|
107
|
+
// 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
|
95
108
|
int64 seconds = 1;
|
96
109
|
|
97
110
|
// Signed fractions of a second at nanosecond resolution of the span
|
@@ -52,6 +52,8 @@ option objc_class_prefix = "GPB";
|
|
52
52
|
// and from RFC 3339 date strings.
|
53
53
|
// See [https://www.ietf.org/rfc/rfc3339.txt](https://www.ietf.org/rfc/rfc3339.txt).
|
54
54
|
//
|
55
|
+
// # Examples
|
56
|
+
//
|
55
57
|
// Example 1: Compute Timestamp from POSIX `time()`.
|
56
58
|
//
|
57
59
|
// Timestamp timestamp;
|
@@ -92,6 +94,29 @@ option objc_class_prefix = "GPB";
|
|
92
94
|
// timestamp = Timestamp()
|
93
95
|
// timestamp.GetCurrentTime()
|
94
96
|
//
|
97
|
+
// # JSON Mapping
|
98
|
+
//
|
99
|
+
// In JSON format, the Timestamp type is encoded as a string in the
|
100
|
+
// [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) format. That is, the
|
101
|
+
// format is "{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z"
|
102
|
+
// where {year} is always expressed using four digits while {month}, {day},
|
103
|
+
// {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional
|
104
|
+
// seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution),
|
105
|
+
// are optional. The "Z" suffix indicates the timezone ("UTC"); the timezone
|
106
|
+
// is required, though only UTC (as indicated by "Z") is presently supported.
|
107
|
+
//
|
108
|
+
// For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past
|
109
|
+
// 01:30 UTC on January 15, 2017.
|
110
|
+
//
|
111
|
+
// In JavaScript, one can convert a Date object to this format using the
|
112
|
+
// standard [toISOString()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString]
|
113
|
+
// method. In Python, a standard `datetime.datetime` object can be converted
|
114
|
+
// to this format using [`strftime`](https://docs.python.org/2/library/time.html#time.strftime)
|
115
|
+
// with the time format spec '%Y-%m-%dT%H:%M:%S.%fZ'. Likewise, in Java, one
|
116
|
+
// can use the Joda Time's [`ISODateTimeFormat.dateTime()`](
|
117
|
+
// http://joda-time.sourceforge.net/apidocs/org/joda/time/format/ISODateTimeFormat.html#dateTime())
|
118
|
+
// to obtain a formatter capable of generating timestamps in this format.
|
119
|
+
//
|
95
120
|
//
|
96
121
|
message Timestamp {
|
97
122
|
|
Binary file
|
data/bin/x86_64-macos/protoc
CHANGED
Binary file
|
@@ -49,7 +49,7 @@ package google.protobuf.compiler;
|
|
49
49
|
option java_package = "com.google.protobuf.compiler";
|
50
50
|
option java_outer_classname = "PluginProtos";
|
51
51
|
|
52
|
-
option go_package = "plugin_go";
|
52
|
+
option go_package = "github.com/golang/protobuf/protoc-gen-go/plugin;plugin_go";
|
53
53
|
|
54
54
|
import "google/protobuf/descriptor.proto";
|
55
55
|
|
@@ -84,6 +84,9 @@ message CodeGeneratorRequest {
|
|
84
84
|
// the entire set into memory at once. However, as of this writing, this
|
85
85
|
// is not similarly optimized on protoc's end -- it will store all fields in
|
86
86
|
// memory at once before sending them to the plugin.
|
87
|
+
//
|
88
|
+
// Type names of fields and extensions in the FileDescriptorProto are always
|
89
|
+
// fully qualified.
|
87
90
|
repeated FileDescriptorProto proto_file = 15;
|
88
91
|
|
89
92
|
// The version number of protocol compiler.
|
@@ -376,6 +376,10 @@ message FileOptions {
|
|
376
376
|
// to prefix the types/symbols defined.
|
377
377
|
optional string swift_prefix = 39;
|
378
378
|
|
379
|
+
// Sets the php class prefix which is prepended to all php generated classes
|
380
|
+
// from this .proto. Default is empty.
|
381
|
+
optional string php_class_prefix = 40;
|
382
|
+
|
379
383
|
// The parser stores options it doesn't recognize here. See above.
|
380
384
|
repeated UninterpretedOption uninterpreted_option = 999;
|
381
385
|
|
@@ -441,7 +445,7 @@ message MessageOptions {
|
|
441
445
|
optional bool map_entry = 7;
|
442
446
|
|
443
447
|
reserved 8; // javalite_serializable
|
444
|
-
|
448
|
+
reserved 9; // javanano_as_lite
|
445
449
|
|
446
450
|
// The parser stores options it doesn't recognize here. See above.
|
447
451
|
repeated UninterpretedOption uninterpreted_option = 999;
|
@@ -561,6 +565,7 @@ message EnumOptions {
|
|
561
565
|
// is a formalization for deprecating enums.
|
562
566
|
optional bool deprecated = 3 [default=false];
|
563
567
|
|
568
|
+
reserved 5; // javanano_as_lite
|
564
569
|
|
565
570
|
// The parser stores options it doesn't recognize here. See above.
|
566
571
|
repeated UninterpretedOption uninterpreted_option = 999;
|
@@ -47,6 +47,8 @@ option objc_class_prefix = "GPB";
|
|
47
47
|
// two Timestamp values is a Duration and it can be added or subtracted
|
48
48
|
// from a Timestamp. Range is approximately +-10,000 years.
|
49
49
|
//
|
50
|
+
// # Examples
|
51
|
+
//
|
50
52
|
// Example 1: Compute Duration from two Timestamps in pseudo code.
|
51
53
|
//
|
52
54
|
// Timestamp start = ...;
|
@@ -87,11 +89,22 @@ option objc_class_prefix = "GPB";
|
|
87
89
|
// duration = Duration()
|
88
90
|
// duration.FromTimedelta(td)
|
89
91
|
//
|
92
|
+
// # JSON Mapping
|
93
|
+
//
|
94
|
+
// In JSON format, the Duration type is encoded as a string rather than an
|
95
|
+
// object, where the string ends in the suffix "s" (indicating seconds) and
|
96
|
+
// is preceded by the number of seconds, with nanoseconds expressed as
|
97
|
+
// fractional seconds. For example, 3 seconds with 0 nanoseconds should be
|
98
|
+
// encoded in JSON format as "3s", while 3 seconds and 1 nanosecond should
|
99
|
+
// be expressed in JSON format as "3.000000001s", and 3 seconds and 1
|
100
|
+
// microsecond should be expressed in JSON format as "3.000001s".
|
101
|
+
//
|
90
102
|
//
|
91
103
|
message Duration {
|
92
104
|
|
93
105
|
// Signed seconds of the span of time. Must be from -315,576,000,000
|
94
|
-
// to +315,576,000,000 inclusive.
|
106
|
+
// to +315,576,000,000 inclusive. Note: these bounds are computed from:
|
107
|
+
// 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
|
95
108
|
int64 seconds = 1;
|
96
109
|
|
97
110
|
// Signed fractions of a second at nanosecond resolution of the span
|
@@ -52,6 +52,8 @@ option objc_class_prefix = "GPB";
|
|
52
52
|
// and from RFC 3339 date strings.
|
53
53
|
// See [https://www.ietf.org/rfc/rfc3339.txt](https://www.ietf.org/rfc/rfc3339.txt).
|
54
54
|
//
|
55
|
+
// # Examples
|
56
|
+
//
|
55
57
|
// Example 1: Compute Timestamp from POSIX `time()`.
|
56
58
|
//
|
57
59
|
// Timestamp timestamp;
|
@@ -92,6 +94,29 @@ option objc_class_prefix = "GPB";
|
|
92
94
|
// timestamp = Timestamp()
|
93
95
|
// timestamp.GetCurrentTime()
|
94
96
|
//
|
97
|
+
// # JSON Mapping
|
98
|
+
//
|
99
|
+
// In JSON format, the Timestamp type is encoded as a string in the
|
100
|
+
// [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) format. That is, the
|
101
|
+
// format is "{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z"
|
102
|
+
// where {year} is always expressed using four digits while {month}, {day},
|
103
|
+
// {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional
|
104
|
+
// seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution),
|
105
|
+
// are optional. The "Z" suffix indicates the timezone ("UTC"); the timezone
|
106
|
+
// is required, though only UTC (as indicated by "Z") is presently supported.
|
107
|
+
//
|
108
|
+
// For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past
|
109
|
+
// 01:30 UTC on January 15, 2017.
|
110
|
+
//
|
111
|
+
// In JavaScript, one can convert a Date object to this format using the
|
112
|
+
// standard [toISOString()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString]
|
113
|
+
// method. In Python, a standard `datetime.datetime` object can be converted
|
114
|
+
// to this format using [`strftime`](https://docs.python.org/2/library/time.html#time.strftime)
|
115
|
+
// with the time format spec '%Y-%m-%dT%H:%M:%S.%fZ'. Likewise, in Java, one
|
116
|
+
// can use the Joda Time's [`ISODateTimeFormat.dateTime()`](
|
117
|
+
// http://joda-time.sourceforge.net/apidocs/org/joda/time/format/ISODateTimeFormat.html#dateTime())
|
118
|
+
// to obtain a formatter capable of generating timestamps in this format.
|
119
|
+
//
|
95
120
|
//
|
96
121
|
message Timestamp {
|
97
122
|
|
Binary file
|
Binary file
|
data/version.rb
CHANGED
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: grpc-tools
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 1.
|
4
|
+
version: 1.4.0
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- grpc Authors
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2017-
|
11
|
+
date: 2017-06-21 00:00:00.000000000 Z
|
12
12
|
dependencies: []
|
13
13
|
description: protoc and the Ruby gRPC protoc plugin
|
14
14
|
email: grpc-io@googlegroups.com
|