swiftiply 0.5.1 → 0.6.0

data/test/TC_Swiftiply/mongrel/evented_hello.rb

@@ -0,0 +1,25 @@
+begin
+	load_attempted ||= false
+	require 'swiftcore/evented_mongrel'
+rescue LoadError => e
+	unless load_attempted
+		load_attempted = true
+		require 'rubygems'
+		retry
+	end
+	raise e
+end
+
+class SimpleHandler < Mongrel::HttpHandler
+	def process(request, response)
+		response.start(200) do |head,out|
+			head["Content-Type"] = "text/plain"
+			out.write("hello!\n")
+		end
+	end
+end
+
+httpserver = Mongrel::HttpServer.new("127.0.0.1", 29998)
+httpserver.register("/hello", SimpleHandler.new)
+httpserver.register("/dir", Mongrel::DirHandler.new("."))
+httpserver.run.join

data/test/TC_Swiftiply/mongrel/swiftiplied_hello.rb

@@ -0,0 +1,25 @@
+begin
+	load_attempted ||= false
+	require 'swiftcore/swiftiplied_mongrel'
+rescue LoadError => e
+	unless load_attempted
+		load_attempted = true
+		require 'rubygems'
+		retry
+	end
+	raise e
+end
+
+class SimpleHandler < Mongrel::HttpHandler
+	def process(request, response)
+		response.start(200) do |head,out|
+			head["Content-Type"] = "text/plain"
+			out.write("hello!\n")
+		end
+	end
+end
+
+httpserver = Mongrel::HttpServer.new("127.0.0.1", 29999)
+httpserver.register("/hello", SimpleHandler.new)
+httpserver.register("/dir", Mongrel::DirHandler.new("."))
+httpserver.run.join

data/test/TC_Swiftiply/mongrel/threaded_hello.rb

@@ -0,0 +1,25 @@
+begin
+	load_attempted ||= false
+	require 'mongrel'
+rescue LoadError => e
+	unless load_attempted
+		load_attempted = true
+		require 'rubygems'
+		retry
+	end
+	raise e
+end
+
+class SimpleHandler < Mongrel::HttpHandler
+	def process(request, response)
+		response.start(200) do |head,out|
+			head["Content-Type"] = "text/plain"
+			out.write("hello!\n")
+		end
+	end
+end
+
+httpserver = Mongrel::HttpServer.new("127.0.0.1", 29997)
+httpserver.register("/hello", SimpleHandler.new)
+httpserver.register("/dir", Mongrel::DirHandler.new("."))
+httpserver.run.join

data/test/TC_Swiftiply/slow_echo_client

@@ -0,0 +1,26 @@
+require 'swiftcore/Swiftiply/swiftiply_client'
+
+class SlowEchoClient < SwiftiplyClientProtocol
+
+	def post_init
+		@httpdata = ''
+		@timer_set = false
+		super
+	end
+			
+	def receive_data data
+		@httpdata << data
+      		
+		unless @timer_set
+			EventMachine.add_timer(2) {self.send_http_data(@httpdata); self.close_connection_after_writing}
+			@timer_set = true
+		end
+	end
+end
+
+if ARGV[0] and ARGV[0].index(/:/) > 0
+	h,p = ARGV[0].split(/:/,2)
+	EventMachine.run { SlowEchoClient.connect(h,p.to_i) }
+else
+	puts "slow_echo_client HOST:PORT"
+end

metadata

@@ -1,10 +1,10 @@
 --- !ruby/object:Gem::Specification 
-rubygems_version: 0.9.2
+rubygems_version: 0.9.4
 specification_version: 1
 name: swiftiply
 version: !ruby/object:Gem::Version 
-  version: 0.5.1
-date: 2007-05-15 00:00:00 +02:00
+  version: 0.6.0
+date: 2007-08-12 00:00:00 +02:00
 summary: A fast clustering proxy for web applications.
 require_paths: 
 - src
@@ -41,127 +41,40 @@ files:
 - bin/swiftiply
 - bin/mongrel_rails
 - bin/swiftiply_mongrel_rails
+- bin/echo_client
 - external/test_support.rb
 - external/package.rb
 - src/swiftcore
-- src/ramaze
+- src/fastfilereader.rb
+- src/swiftcore/types.rb
 - src/swiftcore/Swiftiply.rb
 - src/swiftcore/swiftiplied_mongrel.rb
 - src/swiftcore/evented_mongrel.rb
-- src/ramaze/adapter
-- src/ramaze/adapter/swiftiplied_mongrel.rb
-- src/ramaze/adapter/evented_mongrel.rb
-- test/rails
-- test/merb
-- test/camping
-- test/ramaze
-- test/rails/test
-- test/rails/README
-- test/rails/Rakefile
-- test/rails/app
-- test/rails/components
-- test/rails/config
-- test/rails/db
-- test/rails/doc
-- test/rails/lib
-- test/rails/log
-- test/rails/observe_ram.rb
-- test/rails/public
-- test/rails/script
-- test/rails/tmp
-- test/rails/vendor
-- test/rails/test/fixtures
-- test/rails/test/functional
-- test/rails/test/integration
-- test/rails/test/mocks
-- test/rails/test/unit
-- test/rails/test/test_helper.rb
-- test/rails/test/mocks/development
-- test/rails/test/mocks/test
-- test/rails/app/controllers
-- test/rails/app/helpers
-- test/rails/app/models
-- test/rails/app/views
-- test/rails/app/controllers/application.rb
-- test/rails/app/controllers/tests_controller.rb
-- test/rails/app/helpers/application_helper.rb
-- test/rails/app/views/layouts
-- test/rails/config/environments
-- test/rails/config/database.yml
-- test/rails/config/routes.rb
-- test/rails/config/boot.rb
-- test/rails/config/environment.rb
-- test/rails/config/environments/production.rb
-- test/rails/config/environments/development.rb
-- test/rails/config/environments/test.rb
-- test/rails/config/environments/production_no_caching.rb
-- test/rails/doc/README_FOR_APP
-- test/rails/lib/tasks
-- test/rails/public/images
-- test/rails/public/javascripts
-- test/rails/public/stylesheets
-- test/rails/public/dispatch.rb
-- test/rails/public/dispatch.cgi
-- test/rails/public/dispatch.fcgi
-- test/rails/public/404.html
-- test/rails/public/500.html
-- test/rails/public/index.html
-- test/rails/public/favicon.ico
-- test/rails/public/robots.txt
-- test/rails/public/images/rails.png
-- test/rails/public/javascripts/prototype.js
-- test/rails/public/javascripts/effects.js
-- test/rails/public/javascripts/dragdrop.js
-- test/rails/public/javascripts/controls.js
-- test/rails/public/javascripts/application.js
-- test/rails/script/performance
-- test/rails/script/process
-- test/rails/script/about
-- test/rails/script/breakpointer
-- test/rails/script/console
-- test/rails/script/destroy
-- test/rails/script/generate
-- test/rails/script/runner
-- test/rails/script/server
-- test/rails/script/plugin
-- test/rails/script/performance/benchmarker
-- test/rails/script/performance/profiler
-- test/rails/script/process/reaper
-- test/rails/script/process/spawner
-- test/rails/script/process/inspector
-- test/rails/tmp/sessions
-- test/rails/tmp/sockets
-- test/rails/tmp/cache
-- test/rails/tmp/pids
-- test/rails/vendor/plugins
-- test/ramaze/main.rb
-- test/ramaze/yaml.db
-- test/ramaze/conf
-- test/ramaze/public
-- test/ramaze/src
-- test/ramaze/template
-- test/ramaze/conf/stage.yaml
-- test/ramaze/conf/benchmark.yaml
-- test/ramaze/conf/live.yaml
-- test/ramaze/conf/silent.yaml
-- test/ramaze/conf/debug.yaml
-- test/ramaze/public/js
-- test/ramaze/public/css
-- test/ramaze/public/favicon.ico
-- test/ramaze/public/ramaze.png
-- test/ramaze/public/404.jpg
-- test/ramaze/public/error.zmr
-- test/ramaze/public/js/jquery.js
-- test/ramaze/public/css/ramaze_error.css
-- test/ramaze/public/css/coderay.css
-- test/ramaze/src/element
-- test/ramaze/src/controller
-- test/ramaze/src/model.rb
-- test/ramaze/src/element/page.rb
-- test/ramaze/src/controller/main.rb
-- test/ramaze/template/index.xhtml
+- src/swiftcore/Swiftiply
+- src/swiftcore/Swiftiply/swiftiply_client.rb
+- src/swiftcore/Swiftiply/support_pagecache.rb
+- test/TC_Swiftiply.rb
+- test/TC_ProxyBag.rb
+- test/TC_ProxyBag
+- test/TC_Swiftiply
+- test/TC_ProxyBag/test_serve_static_file
+- test/TC_Swiftiply/mongrel
+- test/TC_Swiftiply/slow_echo_client
+- test/TC_Swiftiply/test_serve_static_file
+- test/TC_Swiftiply/test_serve_normal_proxy
+- test/TC_Swiftiply/test_serve_static_file_from_cachedir
+- test/TC_Swiftiply/test_serve_normal_proxy_with_authentication
+- test/TC_Swiftiply/mongrel/swiftiplied_hello.rb
+- test/TC_Swiftiply/mongrel/evented_hello.rb
+- test/TC_Swiftiply/mongrel/threaded_hello.rb
+- test/TC_Swiftiply/test_serve_static_file_from_cachedir/public
 - ext/swiftiply_parse
+- ext/fastfilereader
 - ext/swiftiply_parse/parse.rl
+- ext/fastfilereader/extconf.rb
+- ext/fastfilereader/rubymain.cpp
+- ext/fastfilereader/mapper.cpp
+- ext/fastfilereader/mapper.h
 test_files: []
 
 rdoc_options: 
@@ -176,17 +89,17 @@ executables:
 - swiftiply
 - mongrel_rails
 - swiftiply_mongrel_rails
-extensions: []
-
+extensions: 
+- ext/fastfilereader/extconf.rb
 requirements: 
-- Eventmachine 0.7.0 or higher.
+- Eventmachine 0.8.1 or higher.
 dependencies: 
 - !ruby/object:Gem::Dependency 
   name: eventmachine
   version_requirement: 
   version_requirements: !ruby/object:Gem::Version::Requirement 
     requirements: 
-    - - ">"
+    - - ">="
       - !ruby/object:Gem::Version 
-        version: 0.0.0
+        version: 0.8.1
     version: 

data/src/ramaze/adapter/evented_mongrel.rb

@@ -1,2 +0,0 @@
-require 'swiftcore/evented_mongrel'
-require 'ramaze/adapter/mongrel'

data/src/ramaze/adapter/swiftiplied_mongrel.rb

@@ -1,2 +0,0 @@
-require 'swiftcore/swiftiplied_mongrel'
-require 'ramaze/adapter/mongrel'

data/test/rails/README

@@ -1,182 +0,0 @@
-== 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.