protobuf 2.6.4-java → 2.6.5-java

data/README.md

@@ -3,21 +3,53 @@
 [![Gem Version](https://badge.fury.io/rb/protobuf.png)](http://badge.fury.io/rb/protobuf)
 [![Build Status](https://secure.travis-ci.org/localshred/protobuf.png?branch=master)](https://travis-ci.org/localshred/protobuf)
 
-***IMPORTANT: Those upgrading from version 1.4.2 to 2.X should read the [UPGRADING.md](https://github.com/localshred/protobuf/blob/master/UPGRADING.md) notes***
+___IMPORTANT: Those upgrading from version 1.4.2 to 2.X should read the
+[UPGRADING.md](https://github.com/localshred/protobuf/blob/master/UPGRADING.md) notes___
 
-Protobuf is an implementation of [Google's protocol buffers][google-pb] in ruby. We currently support version 2.4.1 with support for the new 2.5 coming shortly after it becomes final. It's a gem for managing 3 things:
+Protobuf is an implementation of [Google's protocol buffers][google-pb] in ruby.
+We currently support version 2.4.1 with support for the new 2.5 coming shortly after
+it becomes final.
 
-1. Generating ruby classes from `.proto` files.
-2. Provide an RPC mechanism for calling remote services.
-3. Provide RPC interop between ruby and other protobuf-rpc aware implementations for different languages (e.g. [protobuf-socket-rpc][]).
+---
 
-So let's dive in and see how to work with all three.
+## Install
 
-## 1. Generating ruby classes from `.proto` files
+You will likely need to install protobuf from your favorite package manager
+or from source. This gem currently supports protobuf 2.4.1. You may alternatively
+specify a `PROTOC_SRC` when installing with rubygems (see below).
+
+### OSX Install
+
+```shell
+$ brew install protobuf
+```
+
+### Ubuntu
+```shell
+$ sudo apt-get install -y protobuf
+```
+
+### Gem Install
+
+Once the protobuf package is installed, go ahead and install with rubygems.
+If you'd like to skip installing the protobuf package (above) and specify an
+alternate location for the protobuf package, for instance if you have a custom
+protoc package, then specify it with `PROTOC_SRC=/path/to/src`.
+_Please note that this will void your warranty as it were. If you compiled with
+a custom protobuf package and are having issues it may be difficult to troubleshoot._
 
-_The `protobuf` package is required for compilation. Mac: `brew install protobuf`, Ubuntu: `sudo apt-get install -y protobuf`_
+```shell
+$ gem install protobuf
 
-Protocol Buffers are great because they allow you to clearly define data storage or data transfer packets. Google officially supports Java, C++, and Python for compilation and usage. Let's make it ruby aware!
+# Provide an alternative protoc source directory to build from.
+$ PROTOC_SRC=/path/to/protobuf/src gem install protobuf
+```
+
+## 1. Generating ruby classes from `.proto` files
+
+Protocol Buffers are great because they allow you to clearly define data storage
+or data transfer packets. Google officially supports Java, C++, and Python for
+compilation and usage. Let's make it ruby aware!
 
 Let's say you have a `defs.proto` file that defines a User message.
 
@@ -35,7 +67,10 @@ Now let's compile that definition to ruby:
 $ rprotoc defs.proto --ruby_out ./lib
 ```
 
-The previous line will take whatever is defined in `defs.proto` and output ruby classes to the `./lib` directory, obeying the package directive. Assuming that's all `defs.proto` had defined, `./lib` should now look like this:
+The previous line will take whatever is defined in `defs.proto` and
+output ruby classes to the `./lib` directory, obeying the package
+directive. Assuming that's all `defs.proto` had defined, `./lib`
+should now look like this:
 
 ```
 - lib
@@ -56,9 +91,12 @@ module Foo
 end
 ```
 
-_Note: The generator will pre-define all the classes empty and then re-open to apply the defined fields. This is an optomization to prevent recursive field errors._
+___Note:__ The generator will pre-define all the classes empty and then
+re-open to apply the defined fields. This is an optomization to prevent
+recursive field errors._
 
-The generated class is now just a plain old ruby object and you can use it however you wish.
+The generated class is now just a plain old ruby object and you
+can use it however you wish.
 
 ```ruby
 require 'lib/foo/user.pb'
@@ -77,7 +115,10 @@ user.last_name     # => Christmas
 
 ### Message (de)serialization
 
-Every message object comes ready for serialization or deserialization. Use `serialize_to_string` to write out the byte-string for the message. Use `parse_from_string` on a new message instance to inflate the byte-string back to a message in ruby.
+Every message object comes ready for serialization or deserialization.
+Use `serialize_to_string` to write out the byte-string for the message.
+Use `parse_from_string` on a new message instance to inflate the
+byte-string back to a message in ruby.
 
 ```ruby
 user = Foo::User.new(:first_name => 'Bob')
@@ -90,13 +131,21 @@ inflated_user == user #=> true
 
 ## 2. RPC
 
-RPC is one of many technologies that tries to solve the problem of getting smaller pieces of data from one place to another. Many will argue for or against RPC and its usefulness, but I'm not going to do that here. Google's Protocol Buffers provides support for Services with RPC and that's why you're here.
+RPC is one of many technologies that tries to solve the problem of getting
+smaller pieces of data from one place to another. Many will argue for or
+against RPC and its usefulness, but I'm not going to do that here. Google's
+Protocol Buffers provides support for Services with RPC and that's why you're here.
 
-Any discussion about RPC leads to a discussion about clients and servers and the remote procedures themselves. For our purposes, we'll talk about a `Client` (process that is calling the server/service), a `Service` (the remote procedure), and a `Server` (the process that manages one or more services). We'll start with the Service first.
+Any discussion about RPC leads to a discussion about clients and servers
+and the remote procedures themselves. For our purposes, we'll talk about
+a `Client` (process that is calling the server/service), a `Service`
+(the remote procedure), and a `Server` (the process that manages one or more
+services). We'll start with the Service first.
 
 ### Services
 
-Services are simply classes that have endpoint methods defined. Here's what one looks like in protobuf:
+Services are simply classes that have endpoint methods defined. Here's what
+one looks like in protobuf:
 
 ```
 package foo;
@@ -124,11 +173,15 @@ module Foo
 end
 ```
 
-**Important Note: The UserService class here is a *stub*. You should not provide your implementation in this generated file as subsequent generations will wipe out your implmentation. Read on to learn how to use this stub.**
+__Important Note: The UserService class here is a *stub*. You should not
+provide your implementation in this generated file as subsequent generations
+will wipe out your implmentation. Read on to learn how to use this stub.__
 
 Did you read the note above? Go read it. I'll wait.
 
-Ok, now that you have a generated service stub, you'll want to require it from `lib` and implement the methods. Create a service implementation file in your project. In rails I'd put this in `app/services/user_service.rb`.
+Ok, now that you have a generated service stub, you'll want to require it
+from `lib` and implement the methods. Create a service implementation file
+in your project. In rails I'd put this in `app/services/user_service.rb`.
 
 ```ruby
 # app/services/user_service.rb
@@ -152,15 +205,27 @@ module Foo
 end
 ```
 
-Simply implement the instance method for the defined rpc. You can provide any other methods in this class as helpers, but only those defined in the proto file will be callable by remote clients. Every request made by a client will provide a non-empty request of the defined type. The server creates a new service instance based on the request, so you should not be constrained to just the endpoint method. This is similar to rails controllers where only methods defined by the routes file are hooked up to HTTP requests, but it's very common to implement private methods to aid in code quality and simpilicity.
-
-Every instance has a `request` and `response` object used for fulfilling the call, again, similar to a rails controller action. You should never attempt to modify the `request` object. The `response` object however should be modified or replaced entirely.  If you need to create your own response object (a valid case), simply use `respond_with(new_response)`. The returned object should conform to one of three properties:
+Simply implement the instance method for the defined rpc. You can provide
+any other methods in this class as helpers, but only those defined in the
+proto file will be callable by remote clients. Every request made by a client
+will provide a non-empty request of the defined type. The server creates a new
+service instance based on the request, so you should not be constrained to just
+the endpoint method. This is similar to rails controllers where only methods
+defined by the routes file are hooked up to HTTP requests, but it's very common
+to implement private methods to aid in code quality and simpilicity.
+
+Every instance has a `request` and `response` object used for fulfilling the call,
+again, similar to a rails controller action. You should never attempt to modify the
+`request` object. The `response` object however should be modified or replaced
+entirely. If you need to create your own response object (a valid case), simply use
+`respond_with(new_response)`. The returned object should conform to one of three properties:
 
 1. Response should be of same type as defined by the rpc definition (in this case, `Foo::UserList`), or
 2. Response should be a hash. This hash will be used to construct an instance of the defined type and should therefore conform to the appropriate fields for that type.
 3. Response should respond to the `to_proto` method. The object returned by `to_proto` should be an instance of the defined response type.
 
-If at any time the implementation encounters an error, the client can be instructed of the error using `rpc_failed`:
+If at any time the implementation encounters an error, the client can be
+instructed of the error using `rpc_failed`:
 
 ```ruby
 #...
@@ -174,11 +239,16 @@ end
 #...
 ```
 
-This means that the client's `on_failure` callback will be invoked instead of the `on_success` callback. Read more below on client callbacks. One drawback to the `rpc_failed` approach is that it does not short-circuit the rest of the method. This means that you must explicitly return from the method if you do not wish the remainder to be executed.
+This means that the client's `on_failure` callback will be invoked instead
+of the `on_success` callback. Read more below on client callbacks. One drawback
+to the `rpc_failed` approach is that it does not short-circuit the rest of
+the method. This means that you must explicitly return from the method if
+you do not wish the remainder to be executed.
 
 ### Service Filters
 
-Service Filters provides ActionController-style filter support to service instances, specifically adding `before_filter`, `after_filter`, and `around_filter`.
+Service Filters provides ActionController-style filter support to service
+instances, specifically adding `before_filter`, `after_filter`, and `around_filter`.
 
 ```ruby
 require 'lib/foo/user.pb'
@@ -223,37 +293,74 @@ end
 
 #### Halting execution of rpc request inside a filter
 
-__Around Filters__ – Inside of an around filter, if you wish to halt request processing and return, simply do not `yield` the block. Since the filter is implemented as an instance method, you can use `rpc_failed` or `respond_with` just like you can in the endpoint methods.
+__Around Filters__ – Inside of an around filter, if you wish to halt
+request processing and return, simply do not `yield` the block. Since the
+filter is implemented as an instance method, you can use `rpc_failed`
+or `respond_with` just like you can in the endpoint methods.
 
-__Before Filters__ – Returning `false` from a before filter will cancel any other filter calls which would run afterwards, as well as canceling invocation of the service method. Note: You must actually return false, not just a "falsey" value such as nil.
+__Before Filters__ – Returning `false` from a before filter will cancel
+any other filter calls which would run afterwards, as well as canceling
+invocation of the service method. Note: You must actually return false,
+not just a "falsey" value such as nil.
 
-__After Filters__ – There is no request shortcutting since the after filter runs after the request. Duh.
+__After Filters__ – There is no request shortcutting since the after
+filter runs after the request. Duh.
 
 #### Filter options
 
-The following options can be applied to any of the filters as the final argument in the filter configuration. (See example above).
+The following options can be applied to any of the filters as the final
+argument in the filter configuration. (See example above).
 
-__:if__ – The object supplied to `:if` can either be a symbol/string indicating the instance method to call, or, an object that responds to `call`. The method or callable should return true or false indicating if the filter should be invoked or not. Akin to the `if` keyword.
+__:if__ – The object supplied to `:if` can either be a symbol/string
+indicating the instance method to call, or, an object that responds to `call`.
+The method or callable should return true or false indicating if the
+filter should be invoked or not. Akin to the `if` keyword.
 
-__:unless__ – The opposite of the `:if` option is `:unless`. Accepts the same object types. The method or callable should return true or false indicating if the filter should be invoked or not. Akin to the `unless` keyword.
+__:unless__ – The opposite of the `:if` option is `:unless`. Accepts
+the same object types. The method or callable should return true or
+false indicating if the filter should be invoked or not. Akin to the
+`unless` keyword.
 
-__:only__ – A string/symbol or Array of strings/symbols values that reference instance methods. The names of these methods should be the rpc method you wish to invoke the filter for. Methods not identified in this list would not have the filter applied.
+__:only__ – A string/symbol or Array of strings/symbols values that
+reference instance methods. The names of these methods should be the
+rpc method you wish to invoke the filter for. Methods not identified
+in this list would not have the filter applied.
 
-__:except__ – The opposite of the `:only` option. A string/symbol or Array of strings/symbols values that reference instance methods. The names of these methods should be the rpc method you wish to skip invokation of the given filter. Methods not identified in this list would have the filter applied.
+__:except__ – The opposite of the `:only` option. A string/symbol or
+Array of strings/symbols values that reference instance methods. The
+names of these methods should be the rpc method you wish to skip
+invokation of the given filter. Methods not identified in this list
+would have the filter applied.
 
 ### Servers
 
-A service is nothing without being hooked up to a socket. It's the nerdy kid waiting by the telephone for someone to call without knowing that the phone company disconnected their house. Sad and pathetic. So hook up the phone lines!
+A service is nothing without being hooked up to a socket. It's the
+nerdy kid waiting by the telephone for someone to call without knowing
+that the phone company disconnected their house. Sad and pathetic.
+So hook up the phone lines!
 
 ```
 $ rpc_server -o myserver.com -p 9939 -l ./log/protobuf.log ./config/environment.rb
 ```
 
-The previous call will start a Socket server running on the given host and port which will load your application into memory. You certainly don't have to run rails or any other framework, just make sure you have some kind of file that will load your services all into memory. The server doesn't know where you put your code, so tell it.
-
-Be aware that the server needs to be able to translate the socket stream of bytes into an actual protobuf request object. If the definition for that request object aren't known to the server, you're going to have a long day getting this going. It's necessary to store all your definitions and their generated classes in a shared repository (read: gem) so that both client and server have access to the ruby classes in their respective load paths.
-
-Once the server starts, you should see it as a running process with `ps`. Sending a KILL, QUIT, or TERM signal to the pid will result in shutting the server down gracefully.
+The previous call will start a Socket server running on the given
+host and port which will load your application into memory. You
+certainly don't have to run rails or any other framework, just
+make sure you have some kind of file that will load your services
+all into memory. The server doesn't know where you put your code,
+so tell it.
+
+Be aware that the server needs to be able to translate the socket
+stream of bytes into an actual protobuf request object. If the
+definition for that request object aren't known to the server,
+you're going to have a long day getting this going. It's necessary
+to store all your definitions and their generated classes in a
+shared repository (read: gem) so that both client and server have
+access to the ruby classes in their respective load paths.
+
+Once the server starts, you should see it as a running process
+with `ps`. Sending a KILL, QUIT, or TERM signal to the pid will
+result in shutting the server down gracefully.
 
 ```
 $ ps aux | grep rpc_server
@@ -265,7 +372,8 @@ rpc_server shutdown
 
 ### Clients
 
-A lot of work has gone into making the client calls simple and easy to use yet still powerful. Clients have a DSL that feels very ajaxy.
+A lot of work has gone into making the client calls simple and easy
+to use yet still powerful. Clients have a DSL that feels very ajaxy.
 
 ```ruby
 # require the defs from the shared gem/repo
@@ -303,17 +411,33 @@ Foo::UserService.client.find(req) do |c|
 end
 ```
 
-Many different options can be passed to the `.client` call above (such as `:timeout => 600`). See the `lib/protobuf/rpc/client.rb` and `lib/protobuf/rpc/service.rb` files for more documentation.
+Many different options can be passed to the `.client` call above
+(such as `:timeout => 600`). See the `lib/protobuf/rpc/client.rb`
+and `lib/protobuf/rpc/service.rb` files for more documentation.
 
 ## 3. RPC Interop
 
-The main reason I wrote this gem was to provide a ruby implementation to google's protobuf that worked on the RPC layer with a Java Service layer that was already running [protobuf-socket-rpc][], the supported socket rpc library for protobuf from Google. Other ruby protobuf implementations I've used did not provide this kind of support.
+The main reason I wrote this gem was to provide a ruby implementation
+to google's protobuf that worked on the RPC layer with a Java Service
+layer that was already running [protobuf-socket-rpc][], the supported
+socket rpc library for protobuf from Google. Other ruby protobuf
+implementations I've used did not provide this kind of support.
 
 ## Accreditation & Caveats
 
-It must be noted that this gem was started originally as a fork of the [ruby-protobuf][old gem] gem. Its authors and I were unable to reach a communication point to be able to merge all of my RPC updates in with their master. Unfortunately I just simply couldn't use their RPC code and so I forked the code. Myself and others have significantly changed the internals of the gem, including the rpc implementation, the message/field implementation, and the compiler implementation. These changes were made to address glaring performance and quality issues in the code. The code was initially diverged at their 0.4.0 version.
-
-It should also be noted that there are many more features I haven't really shown here, so please let me know if you have any questions on usage or support for various features. Happy protobufing.
+It must be noted that this gem was started originally as a fork of
+the [ruby-protobuf][old gem] gem. Its authors and I were unable to
+reach a communication point to be able to merge all of my RPC updates
+in with their master. Unfortunately I just simply couldn't use their
+RPC code and so I forked the code. Myself and others have significantly
+changed the internals of the gem, including the rpc implementation, the
+message/field implementation, and the compiler implementation. These
+changes were made to address glaring performance and quality issues
+in the code. The code was initially diverged at their 0.4.0 version.
+
+It should also be noted that there are many more features I haven't
+really shown here, so please let me know if you have any questions
+on usage or support for various features. Happy protobufing.
 
 -- BJ Neilsen, [@localshred][]
 

data/ext/ruby_generator/extconf.rb

@@ -1,8 +1,7 @@
 unless defined?(JRUBY_VERSION)
   begin
     require 'mkmf'
-
-    include_directory = File.expand_path(File.join(File.dirname(__FILE__), "..", "protobuf-2.4.1", "src"))
+    include_directory = File.expand_path(ENV['PROTOC_SRC'] || File.join(File.dirname(__FILE__), "..", "protobuf-2.4.1", "src"))
 
     $CPPFLAGS << " -I#{include_directory}"
     $CPPFLAGS << " -Wall "

data/lib/protobuf/enum.rb

@@ -33,7 +33,7 @@ module Protobuf
     end
 
     def self.name_by_value(value)
-      value.nil? ? nil : @names[value]
+      (!value.nil? && value.respond_to?(:to_i)) ? @names[value.to_i] : nil
     end
 
     def self.valid_tag?(tag)

data/lib/protobuf/version.rb

@@ -1,4 +1,4 @@
 module Protobuf
-  VERSION = '2.6.4'
+  VERSION = '2.6.5'
   PROTOC_VERSION = '2.4.1'
 end

data/spec/lib/protobuf/enum_spec.rb

@@ -53,6 +53,10 @@ describe Protobuf::Enum do
   end
 
   describe '.name_by_value' do
+    it 'get the name by value of the enum given the enum' do 
+      Test::EnumTestType.name_by_value(::Test::EnumTestType::THREE).should eq name
+    end
+
     it 'gets the name of the enum corresponding to the given value (tag)' do
       Test::EnumTestType.name_by_value(tag).should eq name
     end

metadata

@@ -2,7 +2,7 @@
 name: protobuf
 version: !ruby/object:Gem::Version
   prerelease:
-  version: 2.6.4
+  version: 2.6.5
 platform: java
 authors:
 - BJ Neilsen
@@ -10,149 +10,240 @@ authors:
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2013-01-28 00:00:00.000000000Z
+date: 2013-02-09 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport
-  version_requirements: &5666 !ruby/object:Gem::Requirement
+  version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '0'
+        version: !binary |-
+          MA==
+    none: false
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: !binary |-
+          MA==
     none: false
-  requirement: *5666
   prerelease: false
   type: :runtime
 - !ruby/object:Gem::Dependency
   name: ffi
-  version_requirements: &5684 !ruby/object:Gem::Requirement
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: !binary |-
+          MA==
+    none: false
+  requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '0'
+        version: !binary |-
+          MA==
     none: false
-  requirement: *5684
   prerelease: false
   type: :runtime
 - !ruby/object:Gem::Dependency
   name: multi_json
-  version_requirements: &5700 !ruby/object:Gem::Requirement
+  version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '0'
+        version: !binary |-
+          MA==
+    none: false
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: !binary |-
+          MA==
     none: false
-  requirement: *5700
   prerelease: false
   type: :runtime
 - !ruby/object:Gem::Dependency
   name: thor
-  version_requirements: &5716 !ruby/object:Gem::Requirement
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: !binary |-
+          MA==
+    none: false
+  requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '0'
+        version: !binary |-
+          MA==
     none: false
-  requirement: *5716
   prerelease: false
   type: :runtime
 - !ruby/object:Gem::Dependency
   name: eventmachine
-  version_requirements: &5732 !ruby/object:Gem::Requirement
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: !binary |-
+          MA==
+    none: false
+  requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '0'
+        version: !binary |-
+          MA==
     none: false
-  requirement: *5732
   prerelease: false
   type: :development
 - !ruby/object:Gem::Dependency
   name: ffi-rzmq
-  version_requirements: &5750 !ruby/object:Gem::Requirement
+  version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '0'
+        version: !binary |-
+          MA==
+    none: false
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: !binary |-
+          MA==
     none: false
-  requirement: *5750
   prerelease: false
   type: :development
 - !ruby/object:Gem::Dependency
   name: pry
-  version_requirements: &5766 !ruby/object:Gem::Requirement
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: !binary |-
+          MA==
+    none: false
+  requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '0'
+        version: !binary |-
+          MA==
     none: false
-  requirement: *5766
   prerelease: false
   type: :development
 - !ruby/object:Gem::Dependency
   name: pry-nav
-  version_requirements: &5782 !ruby/object:Gem::Requirement
+  version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '0'
+        version: !binary |-
+          MA==
+    none: false
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: !binary |-
+          MA==
     none: false
-  requirement: *5782
   prerelease: false
   type: :development
 - !ruby/object:Gem::Dependency
   name: rake
-  version_requirements: &5798 !ruby/object:Gem::Requirement
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: !binary |-
+          MA==
+    none: false
+  requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '0'
+        version: !binary |-
+          MA==
     none: false
-  requirement: *5798
   prerelease: false
   type: :development
 - !ruby/object:Gem::Dependency
   name: rake-compiler
-  version_requirements: &5814 !ruby/object:Gem::Requirement
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: !binary |-
+          MA==
+    none: false
+  requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '0'
+        version: !binary |-
+          MA==
     none: false
-  requirement: *5814
   prerelease: false
   type: :development
 - !ruby/object:Gem::Dependency
   name: rspec
-  version_requirements: &5830 !ruby/object:Gem::Requirement
+  version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '0'
+        version: !binary |-
+          MA==
+    none: false
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: !binary |-
+          MA==
     none: false
-  requirement: *5830
   prerelease: false
   type: :development
 - !ruby/object:Gem::Dependency
   name: simplecov
-  version_requirements: &5846 !ruby/object:Gem::Requirement
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: !binary |-
+          MA==
+    none: false
+  requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '0'
+        version: !binary |-
+          MA==
     none: false
-  requirement: *5846
   prerelease: false
   type: :development
 - !ruby/object:Gem::Dependency
   name: yard
-  version_requirements: &5862 !ruby/object:Gem::Requirement
+  version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '0'
+        version: !binary |-
+          MA==
+    none: false
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: !binary |-
+          MA==
     none: false
-  requirement: *5862
   prerelease: false
   type: :development
 description: Google Protocol Buffers v2.4.1 Serialization and RPC implementation for Ruby.
@@ -165,9 +256,9 @@ executables:
 extensions: []
 extra_rdoc_files: []
 files:
-- .gitignore
-- .travis.yml
-- .yardopts
+- ".gitignore"
+- ".travis.yml"
+- ".yardopts"
 - Gemfile
 - README.md
 - Rakefile
@@ -426,109 +517,29 @@ require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ! '>='
+  - - ">="
     - !ruby/object:Gem::Version
       segments:
       - 0
       hash: 2
-      version: '0'
+      version: !binary |-
+        MA==
   none: false
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ! '>='
+  - - ">="
     - !ruby/object:Gem::Version
       segments:
       - 0
       hash: 2
-      version: '0'
+      version: !binary |-
+        MA==
   none: false
 requirements: []
 rubyforge_project:
-rubygems_version: 1.8.15
+rubygems_version: 1.8.24
 signing_key:
 specification_version: 3
 summary: Google Protocol Buffers v2.4.1 Serialization and RPC implementation for Ruby.
-test_files:
-- spec/benchmark/tasks.rb
-- spec/functional/embedded_service_spec.rb
-- spec/functional/evented_server_spec.rb
-- spec/functional/socket_server_spec.rb
-- spec/functional/zmq_server_spec.rb
-- spec/lib/protobuf/cli_spec.rb
-- spec/lib/protobuf/enum_spec.rb
-- spec/lib/protobuf/enum_value_spec.rb
-- spec/lib/protobuf/field/int32_field_spec.rb
-- spec/lib/protobuf/logger_spec.rb
-- spec/lib/protobuf/message_spec.rb
-- spec/lib/protobuf/rpc/client_spec.rb
-- spec/lib/protobuf/rpc/connector_spec.rb
-- spec/lib/protobuf/rpc/connectors/base_spec.rb
-- spec/lib/protobuf/rpc/connectors/common_spec.rb
-- spec/lib/protobuf/rpc/connectors/socket_spec.rb
-- spec/lib/protobuf/rpc/connectors/zmq_spec.rb
-- spec/lib/protobuf/rpc/servers/evented_server_spec.rb
-- spec/lib/protobuf/rpc/servers/socket_server_spec.rb
-- spec/lib/protobuf/rpc/servers/zmq/broker_spec.rb
-- spec/lib/protobuf/rpc/servers/zmq/server_spec.rb
-- spec/lib/protobuf/rpc/servers/zmq/util_spec.rb
-- spec/lib/protobuf/rpc/servers/zmq/worker_spec.rb
-- spec/lib/protobuf/rpc/service_dispatcher_spec.rb
-- spec/lib/protobuf/rpc/service_filters_spec.rb
-- spec/lib/protobuf/rpc/service_spec.rb
-- spec/lib/protobuf_spec.rb
-- spec/spec_helper.rb
-- spec/support/all.rb
-- spec/support/packed_field.rb
-- spec/support/server.rb
-- spec/support/test/enum.pb.rb
-- spec/support/test/enum.proto
-- spec/support/test/resource.pb.rb
-- spec/support/test/resource.proto
-- spec/support/test/resource_service.rb
-- spec/support/test_app_file.rb
-- spec/support/tolerance_matcher.rb
-- test/data/data.bin
-- test/data/data_source.py
-- test/data/types.bin
-- test/data/types_source.py
-- test/data/unk.png
-- test/proto/addressbook.pb.rb
-- test/proto/addressbook.proto
-- test/proto/addressbook_base.pb.rb
-- test/proto/addressbook_base.proto
-- test/proto/addressbook_ext.pb.rb
-- test/proto/addressbook_ext.proto
-- test/proto/collision.pb.rb
-- test/proto/collision.proto
-- test/proto/ext_collision.pb.rb
-- test/proto/ext_collision.proto
-- test/proto/ext_range.pb.rb
-- test/proto/ext_range.proto
-- test/proto/float_default.proto
-- test/proto/lowercase.pb.rb
-- test/proto/lowercase.proto
-- test/proto/merge.pb.rb
-- test/proto/merge.proto
-- test/proto/nested.pb.rb
-- test/proto/nested.proto
-- test/proto/optional_field.pb.rb
-- test/proto/optional_field.proto
-- test/proto/packed.pb.rb
-- test/proto/packed.proto
-- test/proto/rpc.proto
-- test/proto/types.pb.rb
-- test/proto/types.proto
-- test/test_addressbook.rb
-- test/test_enum_value.rb
-- test/test_extension.rb
-- test/test_lowercase.rb
-- test/test_message.rb
-- test/test_optional_field.rb
-- test/test_packed_field.rb
-- test/test_parse.rb
-- test/test_repeated_types.rb
-- test/test_serialize.rb
-- test/test_standard_message.rb
-- test/test_types.rb
+test_files: []
 has_rdoc:
-...