curve文件系统元数据proto（代码接口定义，已实现） ## 1、 代码结构和代码目录 curve文件系统是相对于curve块设备比较独立的一块，在当前curve项目的目录下，增加一个一级目录curvefs，curvefs下有自己独立的proto\src\test。  ## 2、 文件系统proto定义 #### 2.1 mds.proto mds.proto /* * Copyright (c) 2020 NetEase Inc. * Licensed under the Apache License, Version 2.0 (the "License"); * you may not use for the specific language governing permissions and * limitations under the License. */ syntax="proto2"; package curvefs.mds; option cc_generic_services = true; enum FSStatusCode { OK = 0; //

ts/1/b/2/6/1b26839be034852e1c0a4ae4215a3f89/p2_1.jpg) gRPC go 介绍 01 gRPC 四种通信模式及落地场景 02 根据 proto 生成 go 桩代码 03 订阅者动态注册 04 发布者消息推送 05 现场案例演示 06 ## gRPC go介绍 ## gRPC是什么？ 1. 什么是gRPC？gRPC go与gRPC的关系是什么？ } message SubscribeResponse { bytes payload = 1; } ## 根据Proto生成桩代码 ## 根据Proto生成桩代码 ##### protoc --go-grpc_out=. --go_out=. pubsub.proto ■ protocol: 这是 Protocol Buffers 编译器的执行命令。 --go-grpc_out=.: 表示当前目录。protocol-gen-go-grpc 插件将会处理 .proto 文件中的服务定义并生成 gRPC 服务器和客户端的接口代码。 --go_out=.: 类似地，这个选项指定了非 gRPC 相关的 Protocol Buffers 消息结构体等 Go 语言代码的输出目录，同样为当前目录。protocol-gen-go 插件会处理 .proto 文件中的消息定义并生成对应的 Go 结构体。 makefile

--mount_freebsd.go protobuf AUTHOR'S CONTRIBUTORS LICENSE Make.protobuf Makefile README.md proto Makefile ## 流利说 ♥ GopherChina2018 Black Friday LICENSE.txt README.md block.go doc.go html new proto field? • Trivial if you just have one proto file • How about a.proto imports b.proto who imports c.proto? • How about a.proto imports b.proto and c.proto both of which import d.proto? • I to reuse code / solution? - 不同语言的 fingerprint 函数实现在不同的地方，有更新总是忘记 • proto 因为 import 太复杂放弃写 protocol Makefile 而直接 copy，人为保证一致性 • proto 生成依赖 go_package option 声明导致没法编译 ## How to share knowledge? ## I ntroducing

the new proto field? Trivial if you just have one proto file How about a.proto imports b.proto who imports c.proto? How about a.proto imports b.proto and c.proto both of which import d.proto? I have to reuse code / solution? 不同语言的 fingerprint 函数实现在不同的地方，有更新总是忘记 proto 因为 import 太复杂放弃写 protoc Makefile 而直接 copy，人为保证一致性 proto 生成依赖 go_package option 声明导致没法编译 How to share knowledge? Introducing Mgoogle/protobuf/any.proto=github.com/golang/protobuf/ptypes/any,Mgoogle/protobuf/ compiler/plugin.proto=github.com/golang/protobuf/protoc-gen-go/plugin,Mgoogle/protobuf/ descriptor.proto=github.com/golan

you have not made any modifications to the default channel name, then the command will return you a proto titled mychannel.block. ## Note You will remain in the CLI container for the remainder of these irrelevant to the change we want to make. We accomplish this by means of the jq tool: configtxlator proto_decode --input config_block.pb --type common.Block | jq .data.data[0].payload.data.config > config config.pb: configtxlator proto_encode --input config.json --type common.Config -output config.pb Next, encode modified_config.json to modified_config.pb: configtxlator proto_encode --input modified_config

方法可以实现一个对象继承另一个对象。以前，继承另一个对象，常常写成下面这样。 const obj = { __proto__: prot, foo: 123, }; ES6 规定 ___proto___ 只有浏览器要部署，其他环境不用部署。如果去除 ___proto___，上面代码就要改成下面这样。 const obj = Object.create(prot); obj.foo ptor 进入标准以后，还会有 Reflect.getOwnPropertyDescriptor 方法。 # __proto__ 属性，Object.setPrototypeOf()，Object.getPrototypeOf() ___proto___ 属性 ___proto___ 属性（前后各两个下划线），用来读取或设置当前对象的 prototype 对象。目前，所有浏览器（包括 IE11）都部署了这个属性。 IE11）都部署了这个属性。 对象的扩展 // es6的写法 var obj = { method: function() { ... } }; obj.__proto__ = someOtherObj; // es5的写法 var obj = Object.create(someOtherObj); obj.method = function() { ... }; 该属性没有写入 ES6 的正文，而是写入了附录，原因是

you have not made any modifications to the default channel name, then the command will return you a proto titled mychannel.block. Note: You will remain in the CLI container for the remainder of these manual irrelevant to the change we want to make. We accomplish this by means of the jq tool: configtxlator proto_decode --input config_block.pb --type common.Block | jq .data.→data[0].payload.data.config > config config.pb: configtxlator proto_encode --input config.json --type common.Config --output config.pb Next, encode modified_config.json to modified_config.pb: configtxlator proto_encode --input modified_config

you have not made any modifications to the default channel name, then the command will return you a proto titled mychannel.block. ## Note You will remain in the CLI container for the remainder of these irrelevant to the change we want to make. We accomplish this by means of the jq tool: configtxlator proto_decode --input config_block.pb --type common.Block | jq .data.data[0].payload.data.config > config config.pb: configtxlator proto_encode --input config.json --type common.Config -output config.pb Next, encode modified_config.json to modified_config.pb: configtxlator proto_encode --input modified_config

you have not made any modifications to the default channel name, then the command will return you a proto titled mychannel.block. ## Note You will remain in the CLI container for the remainder of these irrelevant to the change we want to make. We accomplish this by means of the jq tool: configtxlator proto_decode --input config_block.pb --type common.Block | jq .data.data[0].payload.data.config > config config.pb: configtxlator proto_encode --input config.json --type common.Config -output config.pb Next, encode modified_config.json to modified_config.pb: configtxlator proto_encode --input modified_config

you have not made any modifications to the default channel name, then the command will return you a proto titled mychannel.block. ## Note You will remain in the CLI container for the remainder of these irrelevant to the change we want to make. We accomplish this by means of the jq tool: configtxlator proto_decode --input config_block.pb --type common.Block | jq .data.data[0].payload.data.config > config config.pb: configtxlator proto_encode --input config.json --type common.Config -output config.pb Next, encode modified_config.json to modified_config.pb: configtxlator proto_encode --input modified_config