Alright, this time a small announce going out to *just* the mongrel list so I can get some early testing. There''s a new pre-release of 0.3.13.4 out that includes the win32 version of the gem. ** WIN32 USERS SHOULD INSTALL THIS AND TEST.*** ***** BUT NOT ON PRODUCTION SYSTEMS. ****** As usual, you install it with: sudo gem install mongrel --source=http://mongrel.rubyforge.org/releases/ And this time pick the *right* one for your system. CHANGES * All the outstanding bugs on the rubyforge bug list are now closed off. Reopen any that are not really fixed. * PID files are found when stop/restart and this is now part of the full test suite. * HTTP headers with no spacing at all are now accepted for real I promise and with a test to make sure. * Fixes a *major* problem with how output was processed and Rails locking (I blame the stupid Katana patch, but not really). * FreeBSD 6.1 now throws a brand new Errno exception for closed sockets that nobody else throws. This has caused me to sprinkle "rescue Object" after every socket.close to make sure that--yes--the socket really closes. If anyone wants to try and help changing Ruby''s Socket from "Ultimate Errno Randomness Generator" into something sane then let me know because it''s seriously pissing me the hell off. LOCKING Previously I was under the delusion that Mongrel was running rails and then sending the response outside of any locking. This wasn''t really true for various complex reasons (mainly that I''m a dumbass) but now this is the case. Since most coders cannot get their heads around this to save their lives (myself included), I''ve done this diagram which seems to help: B-E-F-O-R-E 0.3.13.4 request -> lock -> rails -> response -> unlock -> done A-F-T-E-R 0.3.13.4 request -> lock -> rails -> unlock -> response -> done This also probably fixes people who''s Mongrels would lock up sometimes as previously there was a rare chance that if a socket (remember the randomness) got stuck then the process would lock up. Now only one thread locks up (which is still a problem). Please test this release on everything you can and shoot me back results. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support?
On 8/14/06, Zed Shaw <zedshaw at zedshaw.com> wrote:> Alright, this time a small announce going out to *just* the mongrel list > so I can get some early testing. > > There''s a new pre-release of 0.3.13.4 out that includes the win32 > version of the gem. > > ** WIN32 USERS SHOULD INSTALL THIS AND TEST.*** > ***** BUT NOT ON PRODUCTION SYSTEMS. ****** > > As usual, you install it with: > > sudo gem install mongrel --source=http://mongrel.rubyforge.org/releases/ > > And this time pick the *right* one for your system.Seems like the gem index (yaml) contains 0.3.12.4-win32 only. Could you update the index please? I''m checking the patch - now I''ve found that line line shouldn''t be there. This is updated patch against current svn (325) (removes the line, and adds --startup-type) I haven''t tested it yet today. Jano -------------- next part -------------- A non-text attachment was scrubbed... Name: diff Type: application/octet-stream Size: 2689 bytes Desc: not available Url : http://rubyforge.org/pipermail/mongrel-users/attachments/20060814/dda77de9/attachment.obj
On 8/14/06, Jan Svitok <jan.svitok at gmail.com> wrote:> On 8/14/06, Zed Shaw <zedshaw at zedshaw.com> wrote: > > Alright, this time a small announce going out to *just* the mongrel list > > so I can get some early testing. > > > > There''s a new pre-release of 0.3.13.4 out that includes the win32 > > version of the gem. > > > > ** WIN32 USERS SHOULD INSTALL THIS AND TEST.*** > > ***** BUT NOT ON PRODUCTION SYSTEMS. ****** > > > > As usual, you install it with: > > > > sudo gem install mongrel --source=http://mongrel.rubyforge.org/releases/ > > > > And this time pick the *right* one for your system. > > Seems like the gem index (yaml) contains 0.3.12.4-win32 only. Could > you update the index please?I''ve downloaded the gem manually (0.3.13.4-win32), and it doesn''t contain compiled extension. Do you cross-compile or do you use oneclick+ some compiler? (latest oneclick 1.8.4-20 is compiled by msvc and it complained about my vc7 compiler -- config.h line 2) J.
On Mon, 2006-08-14 at 11:33 +0200, Jan Svitok wrote:> On 8/14/06, Zed Shaw <zedshaw at zedshaw.com> wrote: > Seems like the gem index (yaml) contains 0.3.12.4-win32 only. Could > you update the index please? > >>From my checks it''s there:~> gem install mongrel --source=http://mongrel.rubyforge.org/releases/ Attempting local installation of ''mongrel'' Local gem file not found: mongrel*.gem Attempting remote installation of ''mongrel'' Select which gem to install for your platform (i486-linux) 1. mongrel 0.3.13.4 (ruby) 2. mongrel 0.3.12.4 (mswin32) 3. Cancel installation Maybe windows doesn''t like it for some reason? I''ll reload tonight and double check.> I''m checking the patch - now I''ve found that line line shouldn''t be there. > This is updated patch against current svn (325) (removes the line, and > adds --startup-type) > I haven''t tested it yet today.I''ll try working this in today. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support?
On Mon, 2006-08-14 at 14:00 +0200, Jan Svitok wrote:> On 8/14/06, Jan Svitok <jan.svitok at gmail.com> wrote:> I''ve downloaded the gem manually (0.3.13.4-win32), and it doesn''t > contain compiled extension. Do you cross-compile or do you use > oneclick+ some compiler? (latest oneclick 1.8.4-20 is compiled by msvc > and it complained about my vc7 compiler -- config.h line 2)Oh, I see what''s wrong now. I uploaded 0.3.12.4 on accident somehow. I''ll fix it up and try the win32 release again. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support?