JarCastingGrizzly-Protobuf
Grizzly NIO framework filters to encode and decode Google's Protocol Buffers serialized messages.
Grizzly-Protobuf is created and maintained by Chris Molozian (@novabyte).
Code licensed under the Apache License v2.0. Documentation licensed under CC BY 3.0.
Usage
Grizzly-Protobuf is available on Maven Central.
<dependency>
<groupId>me.cmoz.grizzly</groupId>
<artifactId>grizzly-protobuf</artifactId>
<version>1.0.0</version>
</dependency>
If you're not using Maven (or a dependency resolver that's compatible with Maven repositories), you can download the JARs you need for your project from Maven Central.
Filter Types
At the moment there are two filters to choose from:
- FixedLengthProtobufFilter, this uses a fixed length header to store the size of the protobuf message being (de)serialized.
- Varint32ProtobufFilter, this uses
varint32encoding to store the size of the protobuf message being (de)serialized.
If you're not sure which to use, start with the Varint32ProtobufFilter and move to the fixed length header alternative if necessary.
Example
Both filters need a MessageLite type to use to parse all incoming messages.
The example below demonstrates the Person protocol format from the Protocol Buffers Java Tutorial with the Varint32ProtobufFilter. All messages sent/received by the filter chain will (de)serialize to the Person protocol format:
final MessageLite prototype = Person.newBuilder()
.setId(1234)
.setName("John Doe")
.setEmail("[email protected]")
.build();
final FilterChainBuilder serverFilterBuilder = FilterChainBuilder.stateless()
.add(new TransportFilter())
.add(new Varint32ProtobufFilter(prototype.getDefaultInstanceForType()));
For more detailed examples of how to integrate this filter into your code have a look at the test cases.
Developer Notes
The codebase requires the Gradle build tool at version 1.6+ and the Java compiler at version 1.6.0 or greater.
The main external dependency for the project is Grizzly NIO, at 2.3.5 or greater and Protobuf-Java at 2.5.0 (for improved parsing performance see here) although older versions are also supported.
For a full list of dependencies see the build script. All dependencies are downloaded by Gradle during the build process.
Building the codebase
A list of all possible build targets can be displayed by Gradle with gradle tasks.
In a regular write-compile-test cycle use gradle test.
A list of all project dependencies can be displayed by Gradle with gradle dependencies.
It is recommended to run Gradle with the Build Daemon enabled to improve performance. e.g. gradle --daemon once the daemon is running it can be stopped with gradle --stop.
Contribute
All contributions to the documentation and the codebase are very welcome. Feel free to open issues on the tracker wherever the documentation needs improving.
Also, pull requests are always welcome! :)