swiftiply 0.5.0

data/src/swiftcore/swiftiplied_mongrel.rb

@@ -0,0 +1,212 @@
+# This module rewrites pieces of the very good Mongrel web server in
+# order to change it from a threaded application to an event based
+# application running since an EventMachine event loop.  It should
+# be compatible with the existing Mongrel handlers for Rails,
+# Camping, Nitro, etc....
+ 
+begin
+	load_attempted ||= false
+	require 'eventmachine'
+rescue LoadError
+	unless load_attempted
+		load_attempted = true
+		require 'rubygems'
+		retry
+	end
+end
+
+require 'mongrel'
+
+module Mongrel
+	class MongrelProtocol < EventMachine::Connection
+		def self.connect(hostname = nil,port = nil)
+			@hostname ||= hostname
+			@port ||= port
+
+			::EventMachine.connect(@hostname, @port, self) do |conn|
+				conn.set_comm_inactivity_timeout 60
+			end
+		end
+
+		def self.hostname
+			@hostname
+		end
+
+		def self.port
+			@port
+		end
+
+		def connection_completed
+			@completed = true
+		end
+
+		def post_init
+			@parser = HttpParser.new
+			@params = HttpParams.new
+			@nparsed = 0
+			@request = nil
+			@request_len = nil
+			@linebuffer = ''
+		end
+
+		def unbind
+			if @completed
+				self.class.connect
+			else
+				::EventMachine.add_timer(rand(4)) {self.class.connect}
+			end
+		end
+
+		def receive_data data
+			@linebuffer << data
+			@nparsed = @parser.execute(@params, @linebuffer, @nparsed) unless @parser.finished?
+			if @parser.finished?
+				if @request_len.nil?
+					#@request_len = @nparsed + @params[::Mongrel::Const::CONTENT_LENGTH].to_i
+					@request_len = @params[::Mongrel::Const::CONTENT_LENGTH].to_i
+					script_name, path_info, handlers = ::Mongrel::HttpServer::Instance.classifier.resolve(@params[::Mongrel::Const::REQUEST_PATH])
+					if handlers
+						@params[::Mongrel::Const::PATH_INFO] = path_info
+						@params[::Mongrel::Const::SCRIPT_NAME] = script_name
+						@params[::Mongrel::Const::REMOTE_ADDR] = @params[::Mongrel::Const::HTTP_X_FORWARDED_FOR] || ::Socket.unpack_sockaddr_in(get_peername)[1]
+						@notifiers = handlers.select { |h| h.request_notify }
+					end
+					if @request_len > ::Mongrel::Const::MAX_BODY
+						new_buffer = Tempfile.new(::Mongrel::Const::MONGREL_TMP_BASE)
+						new_buffer.binmode
+						new_buffer << @linebuffer[@nparsed..-1]
+						#new_buffer << @linebuffer
+						@linebuffer = new_buffer
+					else
+						@linebuffer = StringIO.new(@linebuffer[@nparsed..-1])
+						#@linebuffer = StringIO.new(@linebuffer)
+					end
+				end
+				if @linebuffer.length >= @request_len
+					::Mongrel::HttpServer::Instance.process_http_request(@params,@linebuffer,self)
+					post_init
+				end
+			elsif @linebuffer.length > ::Mongrel::Const::MAX_HEADER
+				raise ::Mongrel::HttpParserError.new("HEADER is longer than allowed, aborting client early.")
+			end
+		rescue Exception => e
+			close_connection
+			raise e
+		end
+
+		def write data
+			send_data data
+		end
+
+		def closed?
+			false
+		end
+
+	end
+
+	class HttpServer
+		def initialize(host, port, num_processors=(2**30-1), timeout=0)
+			@socket = nil
+			@classifier = URIClassifier.new
+			@host = host
+			@port = port
+			@workers = ThreadGroup.new
+			@timeout = timeout
+			@num_processors = num_processors
+			@death_time = 60
+			self.class.const_set(:Instance,self)
+		end
+
+		def run
+			trap('INT') { raise StopServer }
+			trap('TERM') { raise StopServer }
+			@acceptor = Thread.new do
+				EventMachine.run do
+					begin
+						EventMachine.connect(@host,@port,MongrelProtocol)
+					rescue StopServer
+						EventMachine.stop_event_loop
+					end
+				end
+			end
+		end
+
+		def process_http_request(params,linebuffer,client)
+			if not params[Const::REQUEST_PATH]
+				uri = URI.parse(params[Const::REQUEST_URI])
+				params[Const::REQUEST_PATH] = uri.request_uri
+			end
+
+ 			raise "No REQUEST PATH" if not params[Const::REQUEST_PATH]
+
+			script_name, path_info, handlers = @classifier.resolve(params[Const::REQUEST_PATH])
+
+			if handlers
+				notifiers = handlers.select { |h| h.request_notify }
+				request = HttpRequest.new(params, linebuffer, notifiers)
+
+				# request is good so far, continue processing the response
+				response = HttpResponse.new(client)
+
+				# Process each handler in registered order until we run out or one finalizes the response.
+				handlers.each do |handler|
+					handler.process(request, response)
+					break if response.done
+				end
+
+				# And finally, if nobody closed the response off, we finalize it.
+				unless response.done
+					response.finished
+				end
+			else
+				# Didn't find it, return a stock 404 response.
+				# This code is changed from the Mongrel behavior because a content-length
+				# header MUST accompany all HTTP responses that go into a swiftiply
+				# keepalive connection, so just use the Response object to construct the
+				# 404 response.
+				response.status = 404
+				response.body = "#{params[Const::REQUEST_PATH]} not found"
+				response.finished
+			end
+		end
+	end
+
+	class HttpRequest
+		def initialize(params, linebuffer, dispatchers)
+			@params = params
+			@dispatchers = dispatchers
+			@body = linebuffer
+		end
+	end
+
+	class HttpResponse
+		def send_file(path, small_file = false)
+			File.open(path, "rb") do |f|
+				while chunk = f.read(Const::CHUNK_SIZE) and chunk.length > 0
+					begin
+						write(chunk)
+					rescue Object => exc
+						break
+					end
+				end
+			end
+			@body_sent = true
+		end
+
+		def write(data)
+			@socket.send_data data
+		end
+
+		def socket_error(details)
+			@socket.close_connection
+			done = true
+			raise details
+		end
+
+		def finished
+			send_status
+			send_header
+			send_body
+		end
+	end
+end

data/swiftiply.gemspec

@@ -0,0 +1,41 @@
+#####
+# Swiftcore Analogger
+#   http://analogger.swiftcore.org
+#   Copyright 2007 Kirk Haines
+#
+#   Licensed under the Ruby License.  See the README for details.
+#
+#####
+
+spec = Gem::Specification.new do |s|
+  s.name              = 'swiftiply'
+  s.author            = %q(Kirk Haines)
+  s.email             = %q(wyhaines@gmail.com)
+  s.version           = '0.5.0'
+  s.summary           = %q(A fast clustering proxy for web applications.)
+  s.platform          = Gem::Platform::RUBY
+
+  s.has_rdoc          = true
+  s.rdoc_options      = %w(--title Swiftcore::Swiftiply --main README --line-numbers)
+  s.extra_rdoc_files  = %w(README)
+
+  s.files = Dir['**/*']
+	s.executables = %w(swiftiply mongrel_rails swiftiply_mongrel_rails)
+	s.require_paths = %w(src)
+
+	s.requirements      << "Eventmachine 0.7.0 or higher."
+	s.add_dependency('eventmachine')
+  s.test_files = []
+
+  s.rubyforge_project = %q(swiftiply)
+  s.homepage          = %q(http://swiftiply.swiftcore.org/)
+  description         = []
+  File.open("README") do |file|
+    file.each do |line|
+      line.chomp!
+      break if line.empty?
+      description << "#{line.gsub(/\[\d\]/, '')}"
+    end
+  end
+  s.description = description[1..-1].join(" ")
+end

data/test/rails/README

@@ -0,0 +1,182 @@
+== Welcome to Rails
+
+Rails is a web-application and persistence framework that includes everything
+needed to create database-backed web-applications according to the
+Model-View-Control pattern of separation. This pattern splits the view (also
+called the presentation) into "dumb" templates that are primarily responsible
+for inserting pre-built data in between HTML tags. The model contains the
+"smart" domain objects (such as Account, Product, Person, Post) that holds all
+the business logic and knows how to persist themselves to a database. The
+controller handles the incoming requests (such as Save New Account, Update
+Product, Show Post) by manipulating the model and directing data to the view.
+
+In Rails, the model is handled by what's called an object-relational mapping
+layer entitled Active Record. This layer allows you to present the data from
+database rows as objects and embellish these data objects with business logic
+methods. You can read more about Active Record in
+link:files/vendor/rails/activerecord/README.html.
+
+The controller and view are handled by the Action Pack, which handles both
+layers by its two parts: Action View and Action Controller. These two layers
+are bundled in a single package due to their heavy interdependence. This is
+unlike the relationship between the Active Record and Action Pack that is much
+more separate. Each of these packages can be used independently outside of
+Rails.  You can read more about Action Pack in
+link:files/vendor/rails/actionpack/README.html.
+
+
+== Getting started
+
+1. At the command prompt, start a new rails application using the rails command
+   and your application name. Ex: rails myapp
+   (If you've downloaded rails in a complete tgz or zip, this step is already done)
+2. Change directory into myapp and start the web server: <tt>script/server</tt> (run with --help for options)
+3. Go to http://localhost:3000/ and get "Welcome aboard: You’re riding the Rails!"
+4. Follow the guidelines to start developing your application
+
+
+== Web Servers
+
+By default, Rails will try to use Mongrel and lighttpd if they are installed, otherwise
+Rails will use the WEBrick, the webserver that ships with Ruby. When you run script/server,
+Rails will check if Mongrel exists, then lighttpd and finally fall back to WEBrick. This ensures
+that you can always get up and running quickly.
+
+Mongrel is a Ruby-based webserver with a C-component (which requires compilation) that is
+suitable for development and deployment of Rails applications. If you have Ruby Gems installed,
+getting up and running with mongrel is as easy as: <tt>gem install mongrel</tt>.
+More info at: http://mongrel.rubyforge.org
+
+If Mongrel is not installed, Rails will look for lighttpd. It's considerably faster than
+Mongrel and WEBrick and also suited for production use, but requires additional
+installation and currently only works well on OS X/Unix (Windows users are encouraged
+to start with Mongrel). We recommend version 1.4.11 and higher. You can download it from
+http://www.lighttpd.net.
+
+And finally, if neither Mongrel or lighttpd are installed, Rails will use the built-in Ruby
+web server, WEBrick. WEBrick is a small Ruby web server suitable for development, but not
+for production.
+
+But of course its also possible to run Rails on any platform that supports FCGI.
+Apache, LiteSpeed, IIS are just a few. For more information on FCGI,
+please visit: http://wiki.rubyonrails.com/rails/pages/FastCGI
+
+
+== Debugging Rails
+
+Have "tail -f" commands running on the server.log and development.log. Rails will
+automatically display debugging and runtime information to these files. Debugging
+info will also be shown in the browser on requests from 127.0.0.1.
+
+
+== Breakpoints
+
+Breakpoint support is available through the script/breakpointer client. This
+means that you can break out of execution at any point in the code, investigate
+and change the model, AND then resume execution! Example:
+
+  class WeblogController < ActionController::Base
+    def index
+      @posts = Post.find(:all)
+      breakpoint "Breaking out from the list"
+    end
+  end
+
+So the controller will accept the action, run the first line, then present you
+with a IRB prompt in the breakpointer window. Here you can do things like:
+
+Executing breakpoint "Breaking out from the list" at .../webrick_server.rb:16 in 'breakpoint'
+
+  >> @posts.inspect
+  => "[#<Post:0x14a6be8 @attributes={\"title\"=>nil, \"body\"=>nil, \"id\"=>\"1\"}>,
+       #<Post:0x14a6620 @attributes={\"title\"=>\"Rails you know!\", \"body\"=>\"Only ten..\", \"id\"=>\"2\"}>]"
+  >> @posts.first.title = "hello from a breakpoint"
+  => "hello from a breakpoint"
+
+...and even better is that you can examine how your runtime objects actually work:
+
+  >> f = @posts.first
+  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
+  >> f.
+  Display all 152 possibilities? (y or n)
+
+Finally, when you're ready to resume execution, you press CTRL-D
+
+
+== Console
+
+You can interact with the domain model by starting the console through <tt>script/console</tt>.
+Here you'll have all parts of the application configured, just like it is when the
+application is running. You can inspect domain models, change values, and save to the
+database. Starting the script without arguments will launch it in the development environment.
+Passing an argument will specify a different environment, like <tt>script/console production</tt>.
+
+To reload your controllers and models after launching the console run <tt>reload!</tt>
+
+To reload your controllers and models after launching the console run <tt>reload!</tt>
+
+
+
+== Description of contents
+
+app
+  Holds all the code that's specific to this particular application.
+
+app/controllers
+  Holds controllers that should be named like weblogs_controller.rb for
+  automated URL mapping. All controllers should descend from ApplicationController
+  which itself descends from ActionController::Base.
+
+app/models
+  Holds models that should be named like post.rb.
+  Most models will descend from ActiveRecord::Base.
+
+app/views
+  Holds the template files for the view that should be named like
+  weblogs/index.rhtml for the WeblogsController#index action. All views use eRuby
+  syntax.
+
+app/views/layouts
+  Holds the template files for layouts to be used with views. This models the common
+  header/footer method of wrapping views. In your views, define a layout using the
+  <tt>layout :default</tt> and create a file named default.rhtml. Inside default.rhtml,
+  call <% yield %> to render the view using this layout.
+
+app/helpers
+  Holds view helpers that should be named like weblogs_helper.rb. These are generated
+  for you automatically when using script/generate for controllers. Helpers can be used to
+  wrap functionality for your views into methods.
+
+config
+  Configuration files for the Rails environment, the routing map, the database, and other dependencies.
+
+components
+  Self-contained mini-applications that can bundle together controllers, models, and views.
+
+db
+  Contains the database schema in schema.rb.  db/migrate contains all
+  the sequence of Migrations for your schema.
+
+doc
+  This directory is where your application documentation will be stored when generated
+  using <tt>rake doc:app</tt>
+
+lib
+  Application specific libraries. Basically, any kind of custom code that doesn't
+  belong under controllers, models, or helpers. This directory is in the load path.
+
+public
+  The directory available for the web server. Contains subdirectories for images, stylesheets,
+  and javascripts. Also contains the dispatchers and the default HTML files. This should be
+  set as the DOCUMENT_ROOT of your web server.
+
+script
+  Helper scripts for automation and generation.
+
+test
+  Unit and functional tests along with fixtures. When using the script/generate scripts, template
+  test files will be generated for you and placed in this directory.
+
+vendor
+  External libraries that the application depends on. Also includes the plugins subdirectory.
+  This directory is in the load path.

data/test/rails/Rakefile

@@ -0,0 +1,10 @@
+# Add your own tasks in files placed in lib/tasks ending in .rake,
+# for example lib/tasks/capistrano.rake, and they will automatically be available to Rake.
+
+require(File.join(File.dirname(__FILE__), 'config', 'boot'))
+
+require 'rake'
+require 'rake/testtask'
+require 'rake/rdoctask'
+
+require 'tasks/rails'