Chiebot-Mirror
/
googleapis
8
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Public interface definitions of Google APIs. Topics (grpc依赖)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
86 Commits
11 Branches
1 Tag
265 MiB
 
 
Tag: Branch: Tree: 41f2bf6894
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '41f2bf6894'
${ noResults }
Go to file
Ethan Bao 41f2bf6894
Update logging protos and README. 		9 years ago
gapic Converting language gapic yamls to use GapicProviderFactory (#38) 9 years ago
google Update logging protos and README. 9 years ago
.gitignore Ignore google/protobuf package. It should come from protobuf repo. 9 years ago
CONTRIBUTING.md First commit of googleapis repo. It includes several core protobuf 10 years ago
LICENSE First commit of googleapis repo. It includes several core protobuf 10 years ago
Makefile Fix a bug in Makefile that fail to make output directory. 10 years ago
README.md Mention GAPIC in README 9 years ago

README.md

Google APIs

This repository contains the original interface definitions for a small (but growing) set of Google APIs built on a next-generation API serving stack. Reading the original interface definitions can provide a better understanding of these APIs and help you to utilize them more efficiently. You can also use these interface definitions with open source tools to generate client libraries or other artifacts such as documentation.

For more details on all Google APIs and developer tools, see the Google Developers site.

Overview

Google APIs are typically deployed as API services that are hosted under different DNS names. One API service may implement multiple APIs and multiple versions of the same API, and each API contains a collection of API methods.

By default, Google APIs use Protocol Buffers language version 3 - aka proto3 - as their Interface Definition Language (IDL) to define the API interface and the structure of the payload messages. The same interface definition is used for both REST and RPC versions of the API, which can be accessed over different wire protocols.

There are two ways of accessing Google APIs:

  1. JSON over HTTP/1.1: You can access Google APIs directly using JSON over HTTP/1.1, using Google-provided API or third-party API client libraries.

  2. Protocol Buffers over gRPC: You can access Google APIs published in this repository through GRPC, which is a high-performance binary RPC protocol over HTTP/2. It offers many useful features, including request/response multiplex and full-duplex streaming.

Discussions

You may use the Google APIs mailing list for general discussions about this repository.

Repository Structure

This repository uses a directory hierarchy that reflects the Google API product structure. In general, every API has its own root directory, and each major version of the API has its own subdirectory. The proto package names exactly match the directory: this makes it easy to locate the proto definitions and ensures that the generated client libraries have idiomatic namespaces in most programming languages. Alongside the API directories live the configuration files for the GAPIC toolkit.

NOTE: the major version of an API is used to indicate breaking change to the API.

Generate gRPC Source Code

To generate gRPC source code for Google APIs in this repository, you first need to install both Protocol Buffers and gRPC on your local machine. Then you can run make all in this directory to generate the code.

NOTE: The Makefile needs more improvements.