GeezerVisonThe World Wide Web, restored to 800 pixels of glory. |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites |
GeezerVison is showing android.googlesource.com — platform/external/googleapis - Git at Google Bug: 129998803Clone this repo:
Google APIsThis repository contains the original interface definitions of public Google APIs that support both REST and gRPC protocols. Reading the original interface definitions can provide a better understanding of Google APIs and help you to utilize them more efficiently. You can also use these definitions with open source tools to generate client libraries, documentation, and other artifacts. BuildingBazelThe recommended way to build the API client libraries is through Bazel >= 4.2.2. First, install bazel. To build all libraries: bazel build //... To test all libraries: bazel test //... To build one library in all languages: bazel build //google/example/library/v1/... To build the Java package for one library: bazel build //google/example/library/v1:google-cloud-example-library-v1-java Bazel packages exist in all the libraries for Java, Go, Python, Ruby, Node.js, PHP and C#. OverviewGoogle 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. Google APIs use Protocol Buffers version 3 (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 several ways of accessing Google APIs:
DiscussionsThis repo contains copies of Google API definitions and related files. For discussions or to raise issues about Google API client libraries, GRPC or Google Cloud Client Libraries please refer to the repos associated with each area. Repository StructureThis 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 CodeTo 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 NOTE: The Makefile is only intended to generate source code for the entire repository. It is not for generating linkable client library for a specific API. Please see other repositories under https://github.com/googleapis for generating linkable client libraries. Go gRPC Source CodeIt is difficult to generate Go gRPC source code from this repository, since Go has different directory structure. Please use this repository instead. |
| You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |