Skip to content
main
Switch branches/tags
Code

Latest commit

Motivation:

In an effort to unify the various server and client builders, the
`GrpcServerBuilder` should become an interface and the entire
implementation logic should reside in the `servicetalk-grpc-netty`
module.

Modifications:

- `GrpcServerBuilder` converted to an interface,
- `DefaultGrpcServerBuilder` now contains the entire implementation,
- `CatchAllHttpServiceFilter` moved to `servicetalk-grpc-netty` module
  and became a top level package private class,
- Methods: `GrpcServiceFactory#merge`, `GrpcStatusCode#fromHttp2ErrorCode`
  made public to allow use in the `servicetalk-grpc-netty` module,
- Constants from `GrpcUtils` from the `servicetalk-grpc-api` module were
  moved to new classes: `GrpcHeaderNames` and `GrpcHeaderValues` to allow
  reuse in `servicetalk-grpc-netty`.

Result:

`GrpcServerBuilder` is now an interface which makes it consistent with
the `HttpServerBuilder` interface.
9eb3bf2

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

ServiceTalk

Maven Central Snapshot Publisher Sonatype Snapshot

ServiceTalk is a JVM network application framework with APIs tailored to specific protocols (e.g. HTTP/1.x, HTTP/2.x, etc…​) and supports multiple programming paradigms.

It is built on Netty and is designed to provide most of the performance/scalability benefits of Netty for common networking protocols used in service to service communication. ServiceTalk provides server support and "smart client" like features such as client-side load balancing and service discovery integration.

See the ServiceTalk docs for more information.

Getting Started

ServiceTalk releases are available on Maven Central.

Refer to the ServiceTalk docs for various examples that will get you started with the different features of ServiceTalk.

Note
Builds of the development version are available in Sonatype’s snapshots Maven repository.

Supported JVM

The minimum supported JDK version is 1.8.

Compatibility

ServiceTalk follows SemVer 2.0.0. API/ABI breaking changes will require package renaming for that module to avoid runtime classpath conflicts.

Note
0.x.y releases are not stable and are permitted to break API/ABI.

Contributor Setup

Important
If you’re intending to contribute to ServiceTalk, make sure to first read the contribution guidelines.

ServiceTalk uses Gradle as its build tool and only requires JDK 8 or higher to be pre-installed. ServiceTalk ships with the Gradle Wrapper, which means that there is no need to install Gradle on your machine beforehand.

File Encoding

ServiceTalk’s source code is UTF-8 encoded: make sure your filesystem supports it before attempting to build the project. Setting the JAVA_TOOL_OPTIONS env var to -Dfile.encoding=UTF-8 should help building the project in non-UTF-8 environments. Editors and IDEs must also support UTF-8 in order to successfully edit ServiceTalk’s source code.

Build Commands

You should be able to run the following command to build ServiceTalk and verify that all tests and code quality checks pass:

$ ./gradlew build

The supported IDE is IntelliJ IDEA. In order to generate IntelliJ IDEA project files for ServiceTalk, you can run the following command:

$ ./gradlew idea

When done, running one of following commands would open ServiceTalk in IntelliJ:

Generic
$ idea .
macOS
$ open servicetalk.ipr

Project Communication

We encourage your participation asking questions and helping improve the ServiceTalk project. Github issues and pull requests are the primary mechanisms of participation and communication for ServiceTalk.