gRPC:UpandRunning - CSDN文库

需积分: 5 129 浏览量更新于2023-11-24 评论收藏 4.49MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

资源详情

资源评论

资源推荐

fundamentals of protocol buffers in detail in Chapter 4, but for now you can
think of it as a data serialization mechanism). The service interface
definition is specified in a proto file—an ordinary text file with a .proto
extension. You define gRPC services in ordinary protocol buffer format,
with RPC method parameters and return types specified as protocol buffer
messages. Since the service definition is an extension to the protocol buffer
specification, a special gRPC plug-in is used to generate code from your
proto file.
In our example use case, the 
ProductInfo
 service’s interface can be
defined using protocol buffers as shown in Example 1-1. The service
definition of 
ProductInfo
 is comprised of a service interface definition
where we specify the remote methods, their input and output parameters,
and the type definition (or message formats) of those parameters.
Example 1-1. gRPC service definition of ProductInfo service using protocol
buffers
// ProductInfo.proto 
syntax = "proto3";   
package ecommerce;   
 
service ProductInfo {   
    rpc addProduct(Product) returns (ProductID);   
    rpc getProduct(ProductID) returns (Product);   
} 
 
message Product {   
    string id = 1;   
    string name = 2; 
    string description = 3; 
} 
 
message ProductID {   
    string value = 1; 
}
The service definition begins with specifying the protocol buffer version
(proto3) that we use.
Package names are used to prevent name clashes between protocol
message types and also will be used to generate code.