protobuf 2.2.5-java

data/.gitignore

@@ -0,0 +1,17 @@
+*.gem
+*.swp
+pkg/*
+.bundle
+.rvmrc
+*.log
+coverage
+doc
+.yardoc
+.DS_Store
+*.so
+*.bin
+Gemfile.lock
+tmp/*
+ext/defs
+ext/out
+ext/ruby_generator/protoc-ruby

data/.travis.yml

@@ -0,0 +1,9 @@
+language: ruby
+rvm:
+  - "1.9.2"
+  - "1.9.3"
+  - jruby-19mode
+  - rbx-19mode
+  - ruby-head
+  - jruby-head
+script: NO_COMPILE_TEST_PROTOS=1 bundle exec rake spec

data/.yardopts

@@ -0,0 +1,5 @@
+--no-private
+--hide-void-return
+
+--markup-provider=redcarpet
+--markup=markdown

data/Gemfile

@@ -0,0 +1,3 @@
+source :rubygems
+
+gemspec

data/README.md

@@ -0,0 +1,316 @@
+# 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***
+
+Protobuf is an implementation of [Google's protocol buffers][google-pb] in ruby. We currently support version 2.4.0. It's a gem for managing 3 things:
+
+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.
+
+## 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.
+
+```
+package foo;
+message User {
+  required string first_name = 1;
+  required string last_name = 1;
+}
+
+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:
+
+```
+- lib
+  |- foo
+      |- defs.pb.rb
+```
+
+The generated file `defs.pb.rb` should look something like this:
+
+```ruby
+module Foo
+  class User < ::Protobuf::Message; end
+
+  class User
+    required :string, :first_name, 1
+    required :string, :last_name, 2
+  end
+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._
+
+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'
+
+# dot notation reading/writing fields
+user = Foo::User.new
+user.first_name = "Lloyd"
+user.last_name = "Christmas"
+user.first_name     # => "Lloyd"
+
+# or pass in the fields as a hash to the initializer
+user = Foo::User.new :first_name => "Lloyd", :last_name => "Christmas"
+user.first_name     # => Lloyd
+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.
+
+```ruby
+user = Foo::User.new(:first_name => 'Bob')
+bytes = user.serialize_to_string
+puts bytes #=> binary representation of this message object
+
+inflated_user = Foo::User.new.parse_from_string(bytes)
+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.
+
+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:
+
+```
+package foo;
+message UserRequest {
+  optional string email = 1;
+}
+message UserList {
+  repeated User users = 1;
+}
+service UserService {
+  rpc Find (UserRequest) returns (UserList);
+}
+```
+
+And the equivalent ruby stub for the service (generated with `rprotoc`):
+
+```ruby
+# lib/foo/user.pb.rb
+module Foo
+  # UserRequest and UserList Class definitions not shown (see above for generated output of classes).
+
+  class UserService < ::Protobuf::Rpc::Service
+    rpc :find, UserRequest, UserList
+  end
+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.**
+
+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`.
+
+```ruby
+# app/services/user_service.rb
+require 'lib/foo/user.pb'
+
+# Reopen the class and provide the implementation for each rpc method defined.
+module Foo
+  class UserService
+
+    # request -> Foo::UserRequest
+    # response -> Foo::UserResponse
+    def find
+      # request.email will be the unpacked string that was sent by the client request
+      User.find_by_email(request.email).each do |user|
+        # must only use a proto instance of Foo::User when appending to the `users` field
+        response.users << user.to_proto
+      end
+    end
+
+  end
+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 the 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`:
+
+```ruby
+#...
+def find
+  if request.email.blank?
+    rpc_failed 'Unable to find user without an email'
+  else
+    # query/populate response
+  end
+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.
+
+### Service Filters
+
+Service Filters provides ActionController-style filter support to service instances, specifically adding `before_filter`, `after_filter`, and `around_filter`.
+
+```ruby
+class Foo::UserService < ::Protobuf::Rpc::Service
+  before_filter :start_request_timer
+  after_filter :end_request_timer
+  around_filter :benchmark_request
+
+  # Provide a list of rpc methods to call (or exclude calling) for the given filter(s).
+  # The following two filters are essentially equivalent.
+  before_filter :verify_user_present, :only => [ :update, :delete ]
+  before_filter :verify_user_present, :except => [ :find, :create ]
+
+  # Using if/unless filters options to achieve the same goal, reporting a login after the login has been processed.
+  # Note that you can provide a method name or lambda, but you must return a boolean value.
+  after_filter :report_login, :only => :login, :if => :user_found?
+  after_filter :report_login, :only => :login, :if => lambda { |service| service.response.user_guid.present? }
+  after_filter :report_login, :only => :login, :unless => :user_missing?
+  after_filter :report_login, :only => :login, :unless => lambda { |service| service.response.user_guid.empty? }
+
+  #... rpc instance methods
+
+  private
+
+  def start_request_timer
+    @time_start = Time.now
+  end
+
+  def end_request_timer
+    @time_end = Time.now
+    log_info { ... }
+  end
+
+  def benchmark_request
+    Benchmark.benchmark do
+      yield
+    end
+  end
+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.
+
+__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.
+
+#### Filter options
+
+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.
+
+__: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.
+
+__: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 the phone lines!
+
+```
+$ rpc_server -o myserver.com -p 9939 -l ./log/protobuf.log ./config/environment.rb
+```
+
+The previous call will start an 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
+1234 ... rpc_server myservice.com:9939
+
+$ kill -QUIT 1234
+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.
+
+```ruby
+# require the defs from the shared gem/repo
+require 'sharedgem/foo/user.pb'
+
+# Create a request object for the method we are invoking
+req = Foo::UserRequest.new(:email => 'jeff@gmail.com')
+
+# Use the UserService class to generate a client, invoke the rpc method
+# while passing the request object.
+# We could also simply pass a hash to find.
+Foo::UserService.client.find(req) do |c|
+  # This block will be executed (registering the callbacks)
+  # before the request actualy occurs.
+  # the `c` param in this block is the `.client` object
+  # that is generated from the call above
+
+  # Register a block for execution when the response
+  # is deemed successful from the service. Accepts
+  # the unpacked response as its only parameter
+  c.on_success do |response|
+    response.users.each do |u|
+      puts u.inspect
+    end
+  end
+
+  # Register a block for execution when the response
+  # is deemed a failure. This can be either a client-side
+  # or server-side failure. The object passed the to the
+  # block has a `message` and a `code` attribute
+  # to aid in logging/diagnosing the failure.
+  c.on_failure do |err|
+    puts 'It failed: ' + err.message
+  end
+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.
+
+## 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.
+
+## 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.
+
+-- BJ Neilsen, [@localshred][]
+
+  [google-pb]: http://code.google.com/p/protobuf "Google Protocol Buffers"
+  [protobuf-socket-rpc]: http://code.google.com/p/protobuf-socket-rpc/ "Google's official Socket-RPC library for protobuf"
+  [old gem]: https://github.com/macks/ruby-protobuf "Macks ruby-protobuf on github"
+  [@localshred]: http://twitter.com/localshred "Follow on twitter @localshred"

data/Rakefile

@@ -0,0 +1,29 @@
+$:.push File.expand_path("./", File.dirname(__FILE__))
+$:.push File.expand_path("./spec", File.dirname(__FILE__))
+
+require "rubygems"
+require "rubygems/package_task"
+require "bundler/gem_tasks"
+# require "benchmark/tasks"
+
+require "rspec/core/rake_task"
+
+desc "Default: run specs."
+task :default => :spec
+
+desc "Run specs"
+RSpec::Core::RakeTask.new(:spec)
+
+##
+# rake-compiler
+#
+spec = Gem::Specification.load("protobuf.gemspec")
+
+Gem::PackageTask.new(spec) do |pkg|
+end
+
+if RUBY_PLATFORM =~ /java/
+  require "rake/javaextensiontask"
+else
+  require "rake/extensiontask"
+end

data/UPGRADING.md

@@ -0,0 +1,60 @@
+# Upgrading from 1.X to 2.0
+
+I'm sure I'm missing quite a few of the smaller changes that have been made, but here is a list of changes that should affect any external programs or applications using `protobuf`.
+
+## `rprotoc` changes
+
+* New option `--ruby_out` to specify the output directory to place generated ruby files. If not provided, ruby code will not be generated.
+* Extends `libprotoc` to hook in directly to google's provided compiler mechanism.
+* Removed all previous compiler code including the racc parser, node visitors, etc.
+* See `protoc --help` for default options.
+
+## `rprotoc` generated files changes
+
+* Import `require`s now occur outside of any module or class declaration which solves ruby vm warnings previously seen.
+* Empty inherited Message and Enum classes are pre-defined in the file, then reopened and their fields applied. This solves the issue of recursive field dependencies of two or more types in the same file.
+* Generated DSL lines for message fields include the fully qualified name of the type (e.g. optional `::Protobuf::Field::StringField`, :name, 1)
+* Support for any combination of `packed`, `deprecated`, and `default` as options to pass to a field definition.
+* Services are now generated in the corresponding `.pb.rb` file instead of their own `*_service.rb` files as before.
+
+## `rpc_server` changes
+
+* Removed `--env` option. The running application or program is solely in charge of ensuring it's environment is properly loaded.
+* Removed reading of `PB_CLIENT_TYPE`, `PB_SERVER_TYPE` environment variables. Should use mode switches or custom requires (see below) instead.
+* Removed `--client_socket` in favor of using mode switches. This also means client calls made by the `rpc_server` will run as the same connector type as the given mode (socket, zmq, or evented).
+* Removed `--pre-cache-definitions` switch in favor of always pre-caching for performance.
+* Removed `--gc-pause-serialization` since using `--gc-pause-request` in conjunction was redundant.
+* Removed `--client-type` in favor of mode switches.
+* Removed `--server-type` in favor of mode switches.
+* Added mode switch `--evented`.
+* Added `--threads` to specify number of ZMQ Worker threads to use. Ignored if mode is not zmq.
+* Added `--print-deprecation-warnings` switch to tell the server whether or not to print deprecation warnings on field usage. Enabled by default.
+* See `rpc_server help start` for all options and usage. Note: the `start` task is the default and not necessary when running the `rpc_server`.
+
+## Message changes
+
+* `Message#get_field` usage should now specify either `Message#get_field_by_name` or `Message#get_field_by_tag`, depending on your lookup criteria.
+* Support for STDERR output when accessing a message field which has been defined as `[deprecated=true]`. Deprecated warnings can be skipped by running your application or program with `PB_IGNORE_DEPRECATIONS=1`.
+* Significant internal refactoring which provides huge boosts in speed and efficiency both in accessing/writing Message field values, as well as serialization and deserialization routines.
+* Refactor `Message#to_hash` to delegate hash representations to the field values, simply collecting the display values and returning a hash of fields that are set. This also affects `to_json` output.
+
+## Enum changes
+
+* Add `Enum.fetch` class method to polymorphically retrieve an `EnumValue` object.
+* Add `Enum.value_by_name` to retrieve the corresponding `EnumValue` to the given symbol name.
+* Add `Enum.enum_by_value` to retrieve the corresponding `EnumValue` to the given integer value.
+
+## RPC Service changes
+
+* `async_responder` paradigm is no longer supported.
+* `self.response=` paradigm should be converted to using `respond_with(object)`.
+* Significant internal changes that should not bleed beyond the API but which make maintaining the code much easier.
+
+## RPC Client changes
+
+* In the absence of `PB_CLIENT_TYPE` environment var, you should be requiring the specific connector type specifically. For instance, if you wish to run in zmq mode for client requests, update your Gemfile: `gem 'protobuf', :require => 'protobuf/zmq'`.
+* `:async` option on client calls is no longer recognized.
+
+##  Other changes
+
+* Moved files out of `lib/protobuf/common` folder into `lib/protobuf`. Files affected are logger, wire_type, util. The only update would need to be the require path to these files since the modules were always `Protobuf::{TYPE}`.

data/bin/rpc_server

@@ -0,0 +1,5 @@
+#!/usr/bin/env ruby
+
+require 'protobuf/cli'
+::Protobuf::CLI.start(ARGV)
+

data/bin/rprotoc

@@ -0,0 +1,62 @@
+#!/usr/bin/env ruby
+
+require 'rubygems'
+require 'ffi'
+
+base_dir = File.expand_path(File.join(File.dirname(__FILE__), "..", "lib"))
+
+GENERATOR_FILE_PATH = case
+                      when File.exists?(File.join(base_dir, "ruby_generator.bundle")) then
+                        File.join(base_dir, "ruby_generator.bundle")
+                      when File.exists?(File.join(base_dir, "ruby_generator.dll")) then
+                        File.join(base_dir, "ruby_generator.dll")
+                      else
+                        File.join(base_dir, "ruby_generator.so")
+                      end
+
+unless File.exists?(GENERATOR_FILE_PATH)
+  $stdout << <<-WARNING
+    Cannot locate shared object to plugin to protocol buffers generator.
+    Thought the file would be located at #{GENERATOR_FILE_PATH}
+
+    If you are running on Windows you should compile protocol buffer
+    definitions on another VM and then use those definitions locally.
+
+    Only the compiler is restricted by this.  The definitions should work without issue.
+  WARNING
+  $stdout << $/
+
+  exit 1
+end
+
+module Protobuf
+  module RProtoC
+    extend FFI::Library
+    ffi_lib ::GENERATOR_FILE_PATH
+    attach_function :_rprotoc_extern, [:int, :pointer], :int32
+
+    def self.compile_proto(args)
+      GC.disable # Don't want strings to be GC'd while protoc has them
+      args = args.dup
+      args.unshift("rprotoc")
+      args << "--help" if args.size == 1
+
+      ptr_params = []
+      args.each do |param|
+        ptr_params << ::FFI::MemoryPointer.from_string(param.dup)
+      end
+      ptr_params << nil
+
+      argv = ::FFI::MemoryPointer.new(:pointer, ptr_params.size)
+      ptr_params.each_with_index do |param_pointer, index|
+        argv[index].put_pointer(0, param_pointer)
+      end
+
+      self._rprotoc_extern(ptr_params.compact.size, argv)
+    ensure
+      GC.enable
+    end
+  end
+end
+
+::Protobuf::RProtoC.compile_proto(ARGV)

data/examples/addressbook.pb.rb

@@ -0,0 +1,55 @@
+### Generated by rprotoc. DO NOT EDIT!
+### <proto file: examples/addressbook.proto>
+# package tutorial;
+# 
+# message Person {
+#   required string name = 1;
+#   required int32 id = 2;
+#   optional string email = 3;
+# 
+#   enum PhoneType {
+#     MOBILE = 0;
+#     HOME = 1;
+#     WORK = 2;
+#   }
+# 
+#   message PhoneNumber {
+#     required string number = 1;
+#     optional PhoneType type = 2 [default = HOME];
+#   }
+# 
+#   repeated PhoneNumber phone = 4;
+# }
+# 
+# message AddressBook {
+#   repeated Person person = 1;
+# }
+
+require 'protobuf/message/message'
+require 'protobuf/enum'
+require 'protobuf/message/extend'
+
+module Tutorial
+  class Person < ::Protobuf::Message
+    defined_in __FILE__
+    required :string, :name, 1
+    required :int32, :id, 2
+    optional :string, :email, 3
+    class PhoneType < ::Protobuf::Enum
+      defined_in __FILE__
+      MOBILE = 0
+      HOME = 1
+      WORK = 2
+    end
+    class PhoneNumber < ::Protobuf::Message
+      defined_in __FILE__
+      required :string, :number, 1
+      optional :PhoneType, :type, 2, :default => :HOME
+    end
+    repeated :PhoneNumber, :phone, 4
+  end
+  class AddressBook < ::Protobuf::Message
+    defined_in __FILE__
+    repeated :Person, :person, 1
+  end
+end

data/examples/addressbook.proto

@@ -0,0 +1,24 @@
+package tutorial;
+
+message Person {
+  required string name = 1;
+  required int32 id = 2;
+  optional string email = 3;
+
+  enum PhoneType {
+    MOBILE = 0;
+    HOME = 1;
+    WORK = 2;
+  }
+
+  message PhoneNumber {
+    required string number = 1;
+    optional PhoneType type = 2 [default = HOME];
+  }
+
+  repeated PhoneNumber phone = 4;
+}
+
+message AddressBook {
+  repeated Person person = 1;
+}

data/examples/reading_a_message.rb

@@ -0,0 +1,32 @@
+#!/usr/bin/env ruby
+
+require 'addressbook.pb'
+
+def list_people(address_book)
+  address_book.person.each do |person|
+    puts "Person ID: #{person.id}"
+    puts "  Name: #{person.name}"
+    puts "  E-mail: #{person.email}" unless person.email.empty?
+    person.phone.each do |phone_number|
+      print(case phone_number.type
+            when Tutorial::Person::PhoneType::MOBILE then
+              '  Mobile phone #: '
+            when Tutorial::Person::PhoneType::HOME then
+              '  Home phone #: '
+            when Tutorial::Person::PhoneType::WORK then
+              '  Work phone #: '
+            end)
+      puts phone_number.number
+    end
+  end
+end
+
+unless ARGV.size == 1
+  puts "Usage: #{$0} ADDRESS_BOOK_FILE"
+  exit
+end
+
+address_book = Tutorial::AddressBook.new
+address_book.parse_from_file ARGV[0]
+
+list_people address_book

data/examples/writing_a_message.rb

@@ -0,0 +1,46 @@
+#!/usr/bin/env ruby
+
+require 'addressbook.pb'
+
+def prompt_for_address(person)
+  print 'Enter person ID number: '
+  person.id = STDIN.gets.strip.to_i
+  print 'Enter name: '
+  person.name = STDIN.gets.strip
+  print 'Enter email address (blank for none): '
+  email = STDIN.gets.strip
+  person.email = email unless email.empty?
+
+  loop do
+    print 'Enter a phone number (or leave blank to finish): '
+    break if (number = STDIN.gets.strip).empty?
+
+    person.phone << Tutorial::Person::PhoneNumber.new
+    person.phone.last.number = number
+
+    print 'Is this a mobile, home, or work phone? '
+    person.phone.last.type = 
+      case type = STDIN.gets.strip
+      when 'mobile' then
+        Tutorial::Person::PhoneType::MOBILE
+      when 'home' then
+        Tutorial::Person::PhoneType::HOME
+      when 'work' then
+        Tutorial::Person::PhoneType::WORK
+      else
+        puts 'Unknown phone type; leaving as default value.'
+        nil
+      end
+  end
+end
+
+unless ARGV.size == 1
+  puts "Usage: #{$0} ADDRESS_BOOK_FILE" 
+  exit
+end
+
+address_book = Tutorial::AddressBook.new
+address_book.parse_from_file ARGV[0] if File.exist? ARGV[0]
+address_book.person << Tutorial::Person.new
+prompt_for_address address_book.person.last
+address_book.serialize_to_file ARGV[0]