Нет описания

Daniel Alm b5e7c19cc2 Avoid displaying the comment about setting the generated project's indentation settings when running `make`. 7 лет назад
Assets f9de073b4a Update vendor-grpc script to include roots.pem and update roots.pem version. 8 лет назад
Docker 4904e4567f Update protoc compiler in Docker image and make it smaller 7 лет назад
Examples 12df04f87e move examples under Sources/Examples 7 лет назад
Sources 800cea150f Tweak the visibility of `Handler.call`. 7 лет назад
Tests 4cae6e5625 Fix gRPCTests: 7 лет назад
scripts e8d2b1350b Update Examples to version 0.2.1 + minor cleanup. 8 лет назад
third_party f9de073b4a Update vendor-grpc script to include roots.pem and update roots.pem version. 8 лет назад
.gitignore ac7979d5e0 Ensure that errors in client calls are always provided to the user. 7 лет назад
.gitmodules 63c6acfa40 Move CgRPC, gRPC, and QuickProto to "Sources" directory and add new top-level Package.swift. 9 лет назад
.swift-version 04887237e1 Update .swift-version 8 лет назад
.travis-install.sh 0e9aab62c6 Add support for running CI on macOS as well. 7 лет назад
.travis.yml a964f79f0c Merge pull request #178 from MrMage/run-travis-on-macos 7 лет назад
AUTHORS 0aa90a79ee Relicense to Apache 2, change owners to "the gRPC Authors". 8 лет назад
CONTRIBUTING.md 98a8b64da5 Update README and CONTRIBUTING. 9 лет назад
DOCKER.md 410ff70c78 update PROTOBUF 7 лет назад
LICENSE 0aa90a79ee Relicense to Apache 2, change owners to "the gRPC Authors". 8 лет назад
LINUX.md 93f426875b Update Echo sample path 8 лет назад
Makefile b5e7c19cc2 Avoid displaying the comment about setting the generated project's indentation settings when running `make`. 7 лет назад
OVERVIEW.md a11da8644e Fix font weight formatting in OVERVIEW.md 8 лет назад
PATENTS 36f2bde28e Add PATENTS declaration 9 лет назад
Package.swift 263e66bad2 Use Apple's "fake" zlib package instead of Zewo's real zlib code. 7 лет назад
README.md aa746f8591 Move protoc-gen-swiftgrpc plugin to main Sources directory. 7 лет назад
SwiftGRPC.podspec b39e8fc316 Fix the Podspec by only including `Sources/SwiftGRPC/*.swift`. 7 лет назад
fix-indentation-settings.rb 56652765b2 Add a script to fix the project's indentation settings. 7 лет назад
swift-vendoring.sh.template ffe96e6693 Updating for grpc-1.4.5, WIP. Builds but does not pass tests. 8 лет назад
vendor-boringssl.sh 3252f97e0e Exclude example program - containing main() - from boringssl vendoring. 8 лет назад
vendor-grpc.sh f9de073b4a Update vendor-grpc script to include roots.pem and update roots.pem version. 8 лет назад

README.md

Build Status

Swift gRPC

This repository contains an experimental Swift gRPC API and code generator.

It is intended for use with Apple's swift-protobuf support for Protocol Buffers. Both projects contain code generation plugins for protoc, Google's Protocol Buffer compiler, and both contain libraries of supporting code that is needed to build and run the generated code.

APIs and generated code is provided for both gRPC clients and servers, and can be built either with Xcode or the Swift Package Manager. Support is provided for all four gRPC API styles (Unary, Server Streaming, Client Streaming, and Bidirectional Streaming) and connections can be made either over secure (TLS) or insecure channels.

The Echo example provides a comprehensive demonstration of currently-supported features.

Swift Package Manager builds may also be made on Linux systems. Please see DOCKER.md and LINUX.md for details.

gRPC dependencies are vendored

Swift gRPC includes vendored copies of the gRPC core library and BoringSSL, an OpenSSL fork that is used by the gRPC Core. These are built automatically in Swift Package Manager builds.

Usage

The recommended way to use Swift gRPC is to first define an API using the Protocol Buffer language and then use the Protocol Buffer Compiler and the Swift Protobuf and Swift gRPC plugins to generate the necessary support code.

Getting the dependencies

Binary releases of protoc, the Protocol Buffer Compiler, are available on GitHub.

To build the plugins, run make in the main directory. This uses the Swift Package Manager to build both of the necessary plugins: protoc-gen-swift, which generates Protocol Buffer support code and protoc-gen-swiftgrpc, which generates gRPC interface code.

Using the plugins

To use the plugins, protoc and both plugins should be in your search path. Invoke them with commands like the following:

protoc <your proto files> \
    --swift_out=. \
    --swiftgrpc_out=.

By convention the --swift_out option invokes the protoc-gen-swift plugin and --swiftgrpc_out invokes protoc-gen-swiftgrpc.

Building your project

Most grpc-swift development is done with the Swift Package Manager. For usage in Xcode projects, we rely on the swift package generate-xcodeproj command to generate an Xcode project for the grpc-swift core libraries.

The top-level Makefile uses the Swift Package Manager to generate an Xcode project for the SwiftGRPC package:

$ make

This will create SwiftGRPC.xcodeproj, which you should add to your project, along with setting build dependencies on BoringSSL, CgRPC, gRPC, and CzLib.

Please also note that your project will need to include the SwiftProtobuf.xcodeproj from Swift Protobuf and the source files that you generated with protoc and the plugins.

Please see Echo for a working Xcode-based example and file issues if you find any problems.

Low-level gRPC

While the recommended way to use gRPC is with Protocol Buffers and generated code, at its core gRPC is a powerful HTTP/2-based communication system that can support arbitrary payloads. As such, each gRPC library includes low-level interfaces that can be used to directly build API clients and servers with no generated code. For an example of this in Swift, please see the Simple example.

Having build problems?

grpc-swift depends on Swift, Xcode, and swift-proto. We are currently testing with the following versions:

  • Xcode 9.1
  • Swift 4.0-dev
  • swift-protobuf 1.0.2

License

grpc-swift is released under the same license as gRPC, repeated in LICENSE.

Contributing

Please get involved! See our guidelines for contributing.