rsense-server 0.5.0

data/vendor/gems/puma-2.8.2-java/README.md

@@ -0,0 +1,251 @@
+# Puma: A Ruby Web Server Built For Concurrency
+
+[![Build Status](https://secure.travis-ci.org/puma/puma.png)](http://travis-ci.org/puma/puma) [![Dependency Status](https://gemnasium.com/puma/puma.png)](https://gemnasium.com/puma/puma) <a href="https://codeclimate.com/github/puma/puma"><img src="https://codeclimate.com/github/puma/puma.png" /></a>
+
+## Description
+
+Puma is a simple, fast, threaded, and highly concurrent HTTP 1.1 server for Ruby/Rack applications. Puma is intended for use in both development and production environments. In order to get the best throughput, it is highly recommended that you use a  Ruby implementation with real threads like Rubinius or JRuby.
+
+## Built For Speed &amp; Concurrency
+
+Puma is a simple, fast, and highly concurrent HTTP 1.1 server for Ruby web applications. It can be used with any application that supports Rack, and is considered the replacement for Webrick and Mongrel. It was designed to be the go-to server for [Rubinius](http://rubini.us), but also works well with JRuby and MRI. Puma is intended for use in both development and production environments.
+
+Under the hood, Puma processes requests using a C-optimized Ragel extension (inherited from Mongrel) that provides fast, accurate HTTP 1.1 protocol parsing in a portable way. Puma then serves the request in a thread from an internal thread pool (which you can control). This allows Puma to provide real concurrency for your web application!
+
+With Rubinius 2.0, Puma will utilize all cores on your CPU with real threads, meaning you won't have to spawn multiple processes to increase throughput. You can expect to see a similar benefit from JRuby.
+
+On MRI, there is a Global Interpreter Lock (GIL) that ensures only one thread can be run at a time. But if you're doing a lot of blocking IO (such as HTTP calls to external APIs like Twitter), Puma still improves MRI's throughput by allowing blocking IO to be run concurrently (EventMachine-based servers such as Thin turn off this ability, requiring you to use special libraries). Your mileage may vary. In order to get the best throughput, it is highly recommended that you use a Ruby implementation with real threads like [Rubinius](http://rubini.us) or [JRuby](http://jruby.org).
+
+## Quick Start
+
+The easiest way to get started with Puma is to install it via RubyGems. You can do this easily:
+
+    $ gem install puma
+
+Now you should have the `puma` command available in your PATH, so just do the following in the root folder of your Rack application:
+
+    $ puma app.ru
+
+## Advanced Setup
+
+### Sinatra
+
+You can run your Sinatra application with Puma from the command line like this:
+
+    $ ruby app.rb -s Puma
+
+Or you can configure your application to always use Puma:
+
+    require 'sinatra'
+    configure { set :server, :puma }
+
+If you use Bundler, make sure you add Puma to your Gemfile (see below).
+
+### Rails
+
+First, make sure Puma is in your Gemfile:
+
+    gem 'puma'
+
+Then start your server with the `rails` command:
+
+    $ rails s Puma
+
+### Rackup
+
+You can pass it as an option to `rackup`:
+
+    $ rackup -s Puma
+
+Alternatively, you can modify your `config.ru` to choose Puma by default, by adding the following as the first line:
+
+    #\ -s puma
+
+## Configuration
+
+Puma provides numerous options for controlling the operation of the server. Consult `puma -h` (or `puma --help`) for a full list.
+
+### Thread Pool
+
+Puma utilizes a dynamic thread pool which you can modify. You can set the minimum and maximum number of threads that are available in the pool with the `-t` (or `--threads`) flag:
+
+    $ puma -t 8:32
+
+Puma will automatically scale the number of threads based on how much traffic is present. The current default is `0:16`. Feel free to experiment, but be careful not to set the number of maximum threads to a very large number, as you may exhaust resources on the system (or hit resource limits).
+
+### Clustered mode
+
+Puma 2 offers clustered mode, allowing you to use forked processes to handle multiple incoming requests concurrently, in addition to threads already provided. You can tune the number of workers with the `-w` (or `--workers`) flag:
+
+    $ puma -t 8:32 -w 3
+
+On a ruby implementation that offers native threads, you should tune this number to match the number of cores available.
+Note that threads are still used in clustered mode, and the `-t` thread flag setting is per worker, so `-w 2 -t 16:16` will be 32 threads.
+
+If you're running in Clustered Mode you can optionally choose to preload your application before starting up the workers. This is necessary in order to take advantage of the [Copy on Write](http://en.wikipedia.org/wiki/Copy-on-write) feature introduced in [MRI Ruby 2.0](https://blog.heroku.com/archives/2013/3/6/matz_highlights_ruby_2_0_at_waza). To do this simply specify the `--preload` flag in invocation:
+
+    # CLI invocation
+    $ puma -t 8:32 -w 3 --preload
+
+If you're using a configuration file, use the `preload_app!` method, and be sure to specify your config file's location with the `-C` flag:
+
+    $ puma -C config/puma.rb
+
+    # config/puma.rb
+    threads 8,32
+    workers 3
+    preload_app!
+
+Additionally, you can specify a block in your configuration file that will be run on boot of each worker:
+
+    # config/puma.rb
+    on_worker_boot do
+      # configuration here
+    end
+
+This code can be used to setup the process before booting the application, allowing
+you to do some Puma-specific things that you don't want to embed in your application.
+For instance, you could fire a log notification that a worker booted or send something to statsd.
+This can be called multiple times to add hooks.
+
+If you're preloading your application and using ActiveRecord, it's recommend you setup your connection pool here:
+
+    # config/puma.rb
+    on_worker_boot do
+      ActiveSupport.on_load(:active_record) do
+        ActiveRecord::Base.establish_connection
+      end
+    end
+    
+When you use preload_app, your new code goes all in the master process, and is then copied in the workers (meaning it’s only compatible with cluster mode). General rule is to use preload_app when your workers die often and need fast starts. If you don’t have many workers, you should probably don’t use preload_app.
+
+Note that preload_app can’t be used with phased restart, since phased restart kills and restarts workers one-by-one, and preload_app is all about copying the code of master into the workers.
+
+### Binding TCP / Sockets
+
+In contrast to many other server configs which require multiple flags, Puma simply uses one URI parameter with the `-b` (or `--bind`) flag:
+
+    $ puma -b tcp://127.0.0.1:9292
+
+Want to use UNIX Sockets instead of TCP (which can provide a 5-10% performance boost)? No problem!
+
+    $ puma -b unix:///var/run/puma.sock
+
+If you need to change the permissions of the UNIX socket, just add a umask parameter:
+
+    $ puma -b 'unix:///var/run/puma.sock?umask=0777'
+
+Need a bit of security? Use SSL sockets!
+
+    $ puma -b 'ssl://127.0.0.1:9292?key=path_to_key&cert=path_to_cert'
+
+### Control/Status Server
+
+Puma comes with a builtin status/control app that can be used query and control Puma itself. Here is an example of starting Puma with the control server:
+
+    $ puma --control tcp://127.0.0.1:9293 --control-token foo
+
+This directs Puma to start the control server on localhost port 9293. Additionally, all requests to the control server will need to include `token=foo` as a query parameter. This allows for simple authentication. Check out [status.rb](https://github.com/puma/puma/blob/master/lib/puma/app/status.rb) to see what the app has available.
+
+### Configuration file
+
+You can also provide a configuration file which Puma will use with the `-C` (or `--config`) flag:
+
+    $ puma -C /path/to/config
+
+By default, if no configuration file is specifed, Puma will look for a configuration file at config/puma.rb. If an environment is specified, either via the `-e` and `--environment` flags, or through the `RACK_ENV` environment variable, the default file location will be config/puma/environment_name.rb.
+
+If you want to prevent Puma from looking for a configuration file in those locations, provide a dash as the argument to the `-C` (or `--config`) flag:
+
+    $ puma -C "-"
+
+Take the following [sample configuration](https://github.com/puma/puma/blob/master/examples/config.rb) as inspiration or check out [configuration.rb](https://github.com/puma/puma/blob/master/lib/puma/configuration.rb) to see all available options.
+
+## Restart
+
+Puma includes the ability to restart itself allowing easy upgrades to new versions. When available (MRI, Rubinius, JRuby), Puma performs a "hot restart". This is the same functionality available in *unicorn* and *nginx* which keep the server sockets open between restarts. This makes sure that no pending requests are dropped while the restart is taking place.
+
+To perform a restart, there are 2 builtin mechanisms:
+
+  * Send the `puma` process the `SIGUSR2` signal
+  * Use the status server and issue `/restart`
+
+No code is shared between the current and restarted process, so it should be safe to issue a restart any place where you would manually stop Puma and start it again.
+
+If the new process is unable to load, it will simply exit. You should therefore run Puma under a supervisor when using it in production.
+
+### Normal vs Hot vs Phased Restart
+
+A hot restart means that no requests while deploying your new code will be lost, since the server socket is kept open between restarts.
+
+But beware, hot restart does not mean that the incoming requests won’t hang for multiple seconds while your new code has not fully deployed. If you need a zero downtime and zero hanging requests deploy, you must use phased restart.
+
+When you run pumactl phased-restart, Puma kills workers one-by-one, meaning that at least another worker is still available to serve requests, which lead in zero hanging request (yay!).
+
+But again beware, upgrading an application sometimes involves upgrading the database schema. With phased restart, there may be a moment during the deployment where processes belonging to the previous version and processes belonging to the new version both exist at the same time. Any database schema upgrades you perform must therefore be backwards-compatible with the old application version.
+
+if you perform a lot of database migrations, you probably should not use phased restart and use a normal/hot restart instead (pumactl restart). That way, no code is shared while deploying (in that case, preload_app might help for quicker deployment, see below).
+
+
+### Cleanup Code
+
+Puma isn't able to understand all the resources that your app may use, so it provides a hook in the configuration file you pass to `-C` called `on_restart`. The block passed to `on_restart` will be called, unsurprisingly, just before Puma restarts itself.
+
+You should place code to close global log files, redis connections, etc in this block so that their file descriptors don't leak into the restarted process. Failure to do so will result in slowly running out of descriptors and eventually obscure crashes as the server is restart many times.
+
+### Platform Constraints
+
+Because of various platforms not being implement certain things, the following differences occur when Puma is used on different platforms:
+
+  * **JRuby**, **Windows**: server sockets are not seamless on restart, they must be closed and reopened. These platforms have no way to pass descriptors into a new process that is exposed to ruby
+  * **JRuby**, **Windows**: cluster mode is not supported due to a lack of  fork(2)
+  * **Windows**: daemon mode is not supported due to a lack of fork(2)
+
+## pumactl
+
+`pumactl` is a simple CLI frontend to the control/status app described above.  Please refer to `pumactl --help` for available commands.
+
+## Managing multiple Pumas / init.d / upstart scripts
+
+If you want an easy way to manage multiple scripts at once check [tools/jungle](https://github.com/puma/puma/tree/master/tools/jungle) for init.d and upstart scripts.
+
+## Capistrano deployment
+
+Puma has support for Capistrano3 with an [external gem](https://github.com/seuros/capistrano-puma), you just need require that in Gemfile:
+
+```ruby
+gem 'capistrano3-puma'
+```
+And then execute:
+
+```bash
+bundle
+```
+
+Then add to Capfile
+
+```ruby
+require 'capistrano/puma'
+```
+
+and then
+
+```bash
+$ bundle exec cap puma:start
+$ bundle exec cap puma:restart
+$ bundle exec cap puma:stop
+$ bundle exec cap puma:phased_restart
+```
+
+## Contributing
+
+To run the test suite:
+
+```bash
+$ bundle install
+$ bundle exec rake
+```
+
+## License
+
+Puma is copyright 2013 Evan Phoenix and contributors. It is licensed under the BSD license. See the include LICENSE file for details.

data/vendor/gems/puma-2.8.2-java/Rakefile

@@ -0,0 +1,158 @@
+require "hoe"
+require "rake/extensiontask"
+require "rake/javaextensiontask"
+
+IS_JRUBY = defined?(RUBY_ENGINE) ? RUBY_ENGINE == "jruby" : false
+
+Hoe.plugin :git
+Hoe.plugin :ignore
+
+HOE = Hoe.spec "puma" do
+  self.readme_file    = "README.md"
+  self.urls = %w!http://puma.io https://github.com/puma/puma!
+
+  license "BSD"
+  developer 'Evan Phoenix', 'evan@phx.io'
+
+  spec_extras[:extensions]  = ["ext/puma_http11/extconf.rb"]
+  spec_extras[:executables] = ['puma', 'pumactl']
+  spec_extras[:homepage] = self.urls.first
+
+  require_ruby_version ">= 1.8.7"
+
+  dependency "rack", [">= 1.1", "< 2.0"]
+
+  extra_dev_deps << ["rake-compiler", "~> 0.8.0"]
+end
+
+task :prerelease => [:clobber, :check_manifest, :test]
+
+# hoe/test and rake-compiler don't seem to play well together, so disable
+# hoe/test's .gemtest touch file thingy for now
+HOE.spec.files -= [".gemtest"]
+
+include Hoe::Git
+
+desc "Print the current changelog."
+task "changelog" do
+  tag   = ENV["FROM"] || git_tags.last
+  range = [tag, "HEAD"].compact.join ".."
+  cmd   = "git log #{range} '--format=tformat:%B|||%aN|||%aE|||'"
+  now   = Time.new.strftime "%Y-%m-%d"
+
+  changes = `#{cmd}`.split(/\|\|\|/).each_slice(3).map { |msg, author, email|
+              msg.split(/\n/).reject { |s| s.empty? }.first
+            }.flatten.compact
+
+  $changes = Hash.new { |h,k| h[k] = [] }
+
+  codes = {
+    "!" => :major,
+    "+" => :minor,
+    "*" => :minor,
+    "-" => :bug,
+    "?" => :unknown,
+  }
+
+  codes_re = Regexp.escape codes.keys.join
+
+  changes.each do |change|
+    if change =~ /^\s*([#{codes_re}])\s*(.*)/ then
+      code, line = codes[$1], $2
+    else
+      code, line = codes["?"], change.chomp
+    end
+
+    $changes[code] << line
+  end
+
+  puts "=== #{ENV['VERSION'] || 'NEXT'} / #{now}"
+  puts
+  changelog_section :major
+  changelog_section :minor
+  changelog_section :bug
+  changelog_section :unknown
+  puts
+end
+
+# generate extension code using Ragel (C and Java)
+desc "Generate extension code (C and Java) using Ragel"
+task :ragel
+
+file 'ext/puma_http11/http11_parser.c' => ['ext/puma_http11/http11_parser.rl'] do |t|
+  begin
+    sh "ragel #{t.prerequisites.last} -C -G2 -I ext/puma_http11 -o #{t.name}"
+  rescue
+    fail "Could not build wrapper using Ragel (it failed or not installed?)"
+  end
+end
+task :ragel => ['ext/puma_http11/http11_parser.c']
+
+file 'ext/puma_http11/org/jruby/puma/Http11Parser.java' => ['ext/puma_http11/http11_parser.java.rl'] do |t|
+  begin
+    sh "ragel #{t.prerequisites.last} -J -G2 -I ext/puma_http11 -o #{t.name}"
+  rescue
+    fail "Could not build wrapper using Ragel (it failed or not installed?)"
+  end
+end
+task :ragel => ['ext/puma_http11/org/jruby/puma/Http11Parser.java']
+
+if !IS_JRUBY
+
+# compile extensions using rake-compiler
+# C (MRI, Rubinius)
+Rake::ExtensionTask.new("puma_http11", HOE.spec) do |ext|
+  # place extension inside namespace
+  ext.lib_dir = "lib/puma"
+
+  ext.cross_compile = true
+  ext.cross_platform = ['i386-mswin32-60', 'i386-mingw32']
+  ext.cross_compiling do |spec|
+    # add fat-binary stub only when cross compiling
+    spec.files << "lib/puma/puma_http11.rb"
+  end
+
+  CLEAN.include "lib/puma/{1.8,1.9}"
+  CLEAN.include "lib/puma/puma_http11.rb"
+end
+
+else
+
+# Java (JRuby)
+Rake::JavaExtensionTask.new("puma_http11", HOE.spec) do |ext|
+  ext.lib_dir = "lib/puma"
+end
+
+end
+
+# the following is a fat-binary stub that will be used when
+# require 'puma/puma_http11' and will use either 1.8 or 1.9 version depending
+# on RUBY_VERSION
+file "lib/puma/puma_http11.rb" do |t|
+  File.open(t.name, "w") do |f|
+    f.puts "RUBY_VERSION =~ /(\d+.\d+)/"
+    f.puts 'require "puma/#{$1}/puma_http11"'
+  end
+end
+
+# tests require extension be compiled, but depend on the platform
+if IS_JRUBY
+  task :test => [:java]
+else
+  task :test => [:compile]
+end
+
+namespace :test do
+  desc "Run the integration tests"
+  task :integration do
+    sh "cd test/shell; sh run.sh"
+  end
+
+  desc "Run all tests"
+  if defined?(JRUBY_VERSION) and ENV['TRAVIS']
+    task :all => :test
+  else
+    task :all => [:test, "test:integration"]
+  end
+end
+

data/vendor/gems/puma-2.8.2-java/bin/puma

@@ -0,0 +1,10 @@
+#!/usr/bin/env ruby
+#
+# Copyright (c) 2011 Evan Phoenix
+#
+
+require 'puma/cli'
+
+cli = Puma::CLI.new ARGV
+
+cli.run

data/vendor/gems/puma-2.8.2-java/bin/puma-wild

@@ -0,0 +1,17 @@
+#!/usr/bin/env ruby
+#
+# Copyright (c) 2014 Evan Phoenix
+#
+
+require 'rubygems'
+
+deps = ARGV.shift.split(",").each do |s|
+  name, ver = s.split(":",2)
+  gem name, ver
+end
+
+require 'puma/cli'
+
+cli = Puma::CLI.new ARGV
+
+cli.run

data/vendor/gems/puma-2.8.2-java/bin/pumactl

@@ -0,0 +1,12 @@
+#!/usr/bin/env ruby
+
+require 'puma/control_cli'
+
+cli = Puma::ControlCLI.new ARGV
+
+begin
+  cli.run
+rescue => e
+  STDERR.puts e.message
+  exit 1
+end

data/vendor/gems/puma-2.8.2-java/docs/nginx.md

@@ -0,0 +1,80 @@
+# Nginx configuration example file
+
+This is a very common setup using an upstream. It was adapted from some Capistrano recipe I found on the Internet a while ago.
+
+```
+upstream myapp {
+  server unix:///myapp/tmp/puma.sock;
+}
+
+server {
+  listen 80;
+  server_name myapp.com;
+
+  # ~2 seconds is often enough for most folks to parse HTML/CSS and
+  # retrieve needed images/icons/frames, connections are cheap in
+  # nginx so increasing this is generally safe...
+  keepalive_timeout 5;
+
+  # path for static files
+  root /myapp/public;
+  access_log /myapp/log/nginx.access.log;
+  error_log /myapp/log/nginx.error.log info;
+
+  # this rewrites all the requests to the maintenance.html
+  # page if it exists in the doc root. This is for capistrano's
+  # disable web task
+  if (-f $document_root/maintenance.html) {
+    rewrite  ^(.*)$  /maintenance.html last;
+    break;
+  }
+
+  location / {
+    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+    proxy_set_header Host $http_host;
+
+    # If the file exists as a static file serve it directly without
+    # running all the other rewite tests on it
+    if (-f $request_filename) {
+      break;
+    }
+
+    # check for index.html for directory index
+    # if its there on the filesystem then rewite
+    # the url to add /index.html to the end of it
+    # and then break to send it to the next config rules.
+    if (-f $request_filename/index.html) {
+      rewrite (.*) $1/index.html break;
+    }
+
+    # this is the meat of the rack page caching config
+    # it adds .html to the end of the url and then checks
+    # the filesystem for that file. If it exists, then we
+    # rewite the url to have explicit .html on the end
+    # and then send it on its way to the next config rule.
+    # if there is no file on the fs then it sets all the
+    # necessary headers and proxies to our upstream pumas
+    if (-f $request_filename.html) {
+      rewrite (.*) $1.html break;
+    }
+
+    if (!-f $request_filename) {
+      proxy_pass http://myapp;
+      break;
+    }
+  }
+
+  # Now this supposedly should work as it gets the filenames with querystrings that Rails provides.
+  # BUT there's a chance it could break the ajax calls.
+  location ~* \.(ico|css|gif|jpe?g|png|js)(\?[0-9]+)?$ {
+     expires max;
+     break;
+  }
+
+  # Error pages
+  # error_page 500 502 503 504 /500.html;
+  location = /500.html {
+    root /myapp/current/public;
+  }
+}
+```

data/vendor/gems/puma-2.8.2-java/docs/signals.md

@@ -0,0 +1,42 @@
+The [unix signal](http://en.wikipedia.org/wiki/Unix_signal) is a method of sending messages between [processes](http://en.wikipedia.org/wiki/Process_(computing)). When a signal is sent, the operating system interrupts the target process's normal flow of execution. There are standard signals that are used to stop a process but there are also custom signals that can be used for other purposes. This document is an attempt to list all supported signals that Puma will respond to. In general, signals need only be sent to the master process of a cluster.
+
+## Sending Signals
+
+If you are new to signals it can be useful to see how they can be used. When a process is created in a *nix like operating system it will have a [PID - or process identifier](http://en.wikipedia.org/wiki/Process_identifier) that can be used to send signals to the process. For demonstration we will create an infinitely running process by tailing a file:
+
+```sh
+$ echo "foo" >> my.log
+$ irb
+> pid = Process.spawn 'tail -f my.log'
+```
+
+From here we can see that the tail process is running by using the `ps` command:
+
+```sh
+$ ps aux | grep tail
+schneems        87152   0.0  0.0  2432772    492 s032  S+   12:46PM   0:00.00 tail -f my.log
+```
+
+You can send a signal in Ruby using the [Process module](http://www.ruby-doc.org/core-2.1.1/Process.html#kill-method):
+
+```
+$ irb
+> puts pid
+=> 87152
+Process.detach(pid) # http://ruby-doc.org/core-2.1.1/Process.html#method-c-detach
+Process.kill("TERM", pid)
+```
+
+Now you will see via `ps` that there is no more `tail` process. Sometimes when referring to signals the `SIG` prefix will be used for instance `SIGTERM` is equivalent to sending `TERM` via `Process.kill`.
+
+## Puma Signals
+
+Puma cluster responds to these signals:
+
+- `TTIN` increment the worker count by 1
+- `TTOU` decrement the worker count by 1
+- `TERM` send `TERM` to worker. Worker will attempt to finish then exit.
+- `USR2` restart workers
+- `USR1` restart workers in phases, a rolling restart.
+- `INT` equivalent of sending Ctrl-C to cluster. Will attempt to finish then exit.
+- `CHLD`

data/vendor/gems/puma-2.8.2-java/ext/puma_http11/PumaHttp11Service.java

@@ -0,0 +1,17 @@
+package puma;
+
+import java.io.IOException;
+        
+import org.jruby.Ruby;
+import org.jruby.runtime.load.BasicLibraryService;
+
+import org.jruby.puma.Http11;
+import org.jruby.puma.MiniSSL;
+
+public class PumaHttp11Service implements BasicLibraryService { 
+    public boolean basicLoad(final Ruby runtime) throws IOException {
+        Http11.createHttp11(runtime);
+        MiniSSL.createMiniSSL(runtime);
+        return true;
+    }
+}

data/vendor/gems/puma-2.8.2-java/ext/puma_http11/ext_help.h

@@ -0,0 +1,15 @@
+#ifndef ext_help_h
+#define ext_help_h
+
+#define RAISE_NOT_NULL(T) if(T == NULL) rb_raise(rb_eArgError, "%s", "NULL found for " # T " when shouldn't be.");
+#define DATA_GET(from,type,name) Data_Get_Struct(from,type,name); RAISE_NOT_NULL(name);
+#define REQUIRE_TYPE(V, T) if(TYPE(V) != T) rb_raise(rb_eTypeError, "%s", "Wrong argument type for " # V " required " # T);
+#define ARRAY_SIZE(x) (sizeof(x)/sizeof(x[0]))
+
+#ifdef DEBUG
+#define TRACE()  fprintf(stderr, "> %s:%d:%s\n", __FILE__, __LINE__, __FUNCTION__)
+#else
+#define TRACE() 
+#endif
+
+#endif

data/vendor/gems/puma-2.8.2-java/ext/puma_http11/extconf.rb

@@ -0,0 +1,8 @@
+require 'mkmf'
+
+dir_config("puma_http11")
+
+$defs.push "-Wno-deprecated-declarations"
+$libs += " -lssl -lcrypto "
+
+create_makefile("puma/puma_http11")