about summary refs log tree commit homepage
path: root/lib/mongrel.rb
DateCommit message (Collapse)
2009-02-09s/Mongrel/Unicorn/g
Avoid conflicting with existing Mongrel libraries since we'll be incompatible and break things w/o disrupting Mongrel installations.
2009-02-01Realistic defaults.
2009-01-31Clean up some logging.
2009-01-31No more special params hash.
2009-01-31Remove abstract handler.
2009-01-31Mongrel.run(app, opts)
2009-01-31No more throttling.
2009-01-31Make stop raise if server was not started.
2009-01-31Cleanup.
2009-01-31Cleanup.
2009-01-31Cleanup.
2009-01-31Removed bad requires
2009-01-31Merge pivotal code.
Breaks world. Added option to throttle number of concurrent threads processing requests. Conflicts: bin/mongrel_rails lib/mongrel.rb lib/mongrel/configurator.rb lib/mongrel/rails.rb test/unit/test_ws.rb
2009-01-31Moving toward using a logger instead of dumping to STDERR all over the place.
Remove all non-abstract handlers in favor of Rack. Conflicts: lib/mongrel/command.rb lib/mongrel/configurator.rb lib/mongrel/debug.rb lib/mongrel/handlers.rb lib/mongrel/rails.rb test/unit/test_configurator.rb
2009-01-31Got rake working took out trash
2008-12-04Removed uri_classifier, now we just use racks
2008-12-01Removed configurator completely
2008-11-28Unjoined thread for now. Will fix later.
2008-11-22Join thread at the end of start
2008-11-22removed dispatchers
2008-11-22Non working rack implementation
2008-11-08require 'fcntl' for the Fcntl::FD_CLOEXEC flag
Patch by Jos Backus: > /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel.rb:94:in > `initialize': uninitialized constant > Mongrel::HttpServer::Fcntl (NameError) > > That code doesn't have the defined? test. But even if it did, > it wouldn't work as `fcntl' hadn't been require'd so the > Fcntl::FD_CLOEXEC constant couldn't be available until it was > (if it was available). > > So the right thing to do is to also apply this patch which > explicitly require's `fcntl': This is a followup to r1036 git-svn-id: svn+ssh://rubyforge.org/var/svn/mongrel/trunk@1037 19e92222-5c0b-0410-8929-a290d50e31e9
2008-08-20set close-on-exec flag on listen socket
Original patch from Jos Backus, modified to work on weird platforms where Fcntl::FD_CLOEXEC may not be defined. Jos Backus wrote: > Mongrel, at least in 1.1.4, doesn't set the close-on-exec flag > on the listen socket. This leads to trouble in programs that > use Mongrel and fork other programs (like puppetmasterd, part > of Puppet). For an example, see > http://groups.google.com/group/puppet-dev/browse_thread/thread/463f0f8cfc80cc43 git-svn-id: svn+ssh://rubyforge.org/var/svn/mongrel/trunk@1036 19e92222-5c0b-0410-8929-a290d50e31e9
2008-03-24Backport Eric's changes to the http parser from trunk (Eric Wong).
Apply fix for Ragel 6 (Eric Wong, Ry Dahl). Two tests fail with the new parser (1 failed with the old parser). Needs investigation. Close #12 (mongrel_rails send_signal leaves a filehandle open until gc). Close #14 (mongrel_rails command line option --num-procs does not change the max number of procs). Close #15 (mongrel squashes helpful exception in register method). Close #16, XXX needs audit! (CGIWrapper "options" attr_reader has no corresponding @options variable). Close #20 (Mongrel doesn't erase temporary files during it's operation on windows). Close #19, XXX needs audit! (HttpResponse#reset does not properly reset HeaderOut). Close #22 (gem_plugin should load gems from Gem.path not Gem.dir). Close #23 (mongrel_cluster's mongrel_rails configuration option isn't fully respected). If I had git, being offline wouldn't have resulted in one massive commit. git-svn-id: svn+ssh://rubyforge.org/var/svn/mongrel/branches/stable_1-2@995 19e92222-5c0b-0410-8929-a290d50e31e9
2008-02-20Close #10 (@throttle wrongly treated as seconds instead of 100th of seconds).
git-svn-id: svn+ssh://rubyforge.org/var/svn/mongrel/branches/stable_1-1@966 19e92222-5c0b-0410-8929-a290d50e31e9
2007-12-15close 16319 in 1-1-2
git-svn-id: svn+ssh://rubyforge.org/var/svn/mongrel/branches/stable_1-1@911 19e92222-5c0b-0410-8929-a290d50e31e9
2007-12-15backport #15631 to 1-1-2
git-svn-id: svn+ssh://rubyforge.org/var/svn/mongrel/branches/stable_1-1@897 19e92222-5c0b-0410-8929-a290d50e31e9
2007-11-12close #15539
git-svn-id: svn+ssh://rubyforge.org/var/svn/mongrel/trunk@877 19e92222-5c0b-0410-8929-a290d50e31e9
2007-11-12don't warn about unitted @reason; fix objectspace errors on jruby; make ↵
subproject tasks less noisy git-svn-id: svn+ssh://rubyforge.org/var/svn/mongrel/trunk@876 19e92222-5c0b-0410-8929-a290d50e31e9
2007-11-01oops... gems is quite necessary
git-svn-id: svn+ssh://rubyforge.org/var/svn/mongrel/trunk@865 19e92222-5c0b-0410-8929-a290d50e31e9
2007-11-01reinstate bsd accept filter
git-svn-id: svn+ssh://rubyforge.org/var/svn/mongrel/trunk@858 19e92222-5c0b-0410-8929-a290d50e31e9
2007-10-31Mongrel::Gems helper to deal with Rubygems and ActiveSupport infighting
git-svn-id: svn+ssh://rubyforge.org/var/svn/mongrel/trunk@852 19e92222-5c0b-0410-8929-a290d50e31e9
2007-10-30mongrel_experimental works
git-svn-id: svn+ssh://rubyforge.org/var/svn/mongrel/trunk@846 19e92222-5c0b-0410-8929-a290d50e31e9
2007-10-29no filter on freebsd
git-svn-id: svn+ssh://rubyforge.org/var/svn/mongrel/trunk@837 19e92222-5c0b-0410-8929-a290d50e31e9
2007-10-27use rubygems a little less aggressively
git-svn-id: svn+ssh://rubyforge.org/var/svn/mongrel/trunk@808 19e92222-5c0b-0410-8929-a290d50e31e9
2007-10-27let's say that a minor thread contention issue in the test suite is not a ↵
failure on jruby. on MRI i can determine the scheduling via sleep but jruby does what it wants. git-svn-id: svn+ssh://rubyforge.org/var/svn/mongrel/trunk@785 19e92222-5c0b-0410-8929-a290d50e31e9
2007-10-26move socket close into ensure
git-svn-id: svn+ssh://rubyforge.org/var/svn/mongrel/trunk@784 19e92222-5c0b-0410-8929-a290d50e31e9
2007-10-26break classes into their own files
git-svn-id: svn+ssh://rubyforge.org/var/svn/mongrel/trunk@766 19e92222-5c0b-0410-8929-a290d50e31e9
2007-10-26i think mutex_fix is not used due to fastthread
git-svn-id: svn+ssh://rubyforge.org/var/svn/mongrel/trunk@765 19e92222-5c0b-0410-8929-a290d50e31e9
2007-10-26revert trunk to 1.1
git-svn-id: svn+ssh://rubyforge.org/var/svn/mongrel/trunk@744 19e92222-5c0b-0410-8929-a290d50e31e9
2007-10-26reverts for 1.0.2
git-svn-id: svn+ssh://rubyforge.org/var/svn/mongrel/trunk@741 19e92222-5c0b-0410-8929-a290d50e31e9
2007-10-22classifier faster yet because we don't need to rebuild that string
git-svn-id: svn+ssh://rubyforge.org/var/svn/mongrel/trunk@736 19e92222-5c0b-0410-8929-a290d50e31e9
2007-10-22classifier optimization for only one handler on "/", with unit test
git-svn-id: svn+ssh://rubyforge.org/var/svn/mongrel/trunk@735 19e92222-5c0b-0410-8929-a290d50e31e9
2007-10-22no sense breaking the internal api (@routes => @handler_map again)
git-svn-id: svn+ssh://rubyforge.org/var/svn/mongrel/trunk@730 19e92222-5c0b-0410-8929-a290d50e31e9
2007-10-22mongrel_rails and mongrel_cluster support throttle/timeout appropriately
git-svn-id: svn+ssh://rubyforge.org/var/svn/mongrel/trunk@729 19e92222-5c0b-0410-8929-a290d50e31e9
2007-10-22ruby uriclassifier in place. 3x slower on MRI vs TST; 1.5x slower on JRuby ↵
vs same. surprisingly, for any realistic number of URIs the slowdown is basically linear git-svn-id: svn+ssh://rubyforge.org/var/svn/mongrel/trunk@726 19e92222-5c0b-0410-8929-a290d50e31e9
2007-10-22incomplete benchmark method
git-svn-id: svn+ssh://rubyforge.org/var/svn/mongrel/trunk@724 19e92222-5c0b-0410-8929-a290d50e31e9
2007-10-22pure ruby URIClassifier passes on C and JRuby both; now time to profile and ↵
see if it's worth keeping git-svn-id: svn+ssh://rubyforge.org/var/svn/mongrel/trunk@722 19e92222-5c0b-0410-8929-a290d50e31e9
2007-10-21minor test cleanups
git-svn-id: svn+ssh://rubyforge.org/var/svn/mongrel/trunk@710 19e92222-5c0b-0410-8929-a290d50e31e9
2007-10-19minimal jruby socket test; restore some output redirection; echoe trunk ↵
supports target tasks; don't global rescue socket.close git-svn-id: svn+ssh://rubyforge.org/var/svn/mongrel/trunk@701 19e92222-5c0b-0410-8929-a290d50e31e9