similar to: More newbie questions.. Calling out to CGI, Reusing Responses, Multi-thread..

Hello, So, I grabbed the mongrel_upload_progress code from subversion because I really need something similar for a project I am working on. Anyway, I installed the gem and can''t figure out a few things. 1) I''m not sure what Upload < GemPlugin::Plugin "/handlers" is for 2) How to call the Progress < GemPlugin::Plugin "/handlers" handler. While I

Hi, what is the preferd way to configure/start mongrel? [ ] with Mongrel::Configurator => HttpServer [ ] @var = HttpServer.new(...) @var.run I ask because the only debug methode i have found was in Mongrel::Configurator ;-) @Zed: are you also subscribed on nitro list?! regards Alex

Hello, Just for further reference in case of someone else want to do the same : I wanted to write a mongrel for a CGI app : [[[ require ''cgi'' require ''foo'' cgi = CGI.new if !cgi[''uri''] || (cgi[''uri''] == '''') Foo.error "URI argument is required" end uri = cgi[''uri''] user =

By default, Mongrel will delete the HTTP request body and short circuit calling any handlers if a request is interrupted or incomplete. Unfortunately, this breaks any attempt to correctly handle a partial PUT. (BTW, PUT is *way* more efficient for uploads compared to POST which requires a MIME parsing step.) So, about a month ago I wrote up some patches to Mongrel 0.3.18 that allowed

I''m looking at writing a Mongrel handler that mimics the behavior of the Apache mod_put [1]. It allows for the streaming upload of very large (GB) files; it also supports resumable upload. Before I get too involved, I''d like to ask if my reading of the mongrel source code is correct, i.e. what I want to do isn''t currently possible. Looking at the class

Hi All, First, I''m new to the list, so I''d like to say hello to all fellow mongrelists :) Second, I''d like to ask you if there''s any way to make a simple mongrel script run multithreaded? No rails, just plain old class MyHandler < Mongrel::HttpHandler . . . h = Mongrel::HttpServer.new("127.0.0.1", "80") stuff. Since win32 lacks fork,

Signaling using normal kill(2) is preserved, but the master now prefers to signal workers using a pipe rather than kill(2). Non-graceful signals (:TERM/:KILL) are still sent using kill(2), as they ask for immediate shutdown. This change is necessary to avoid triggering the ubf (unblocking function) for rb_thread_call_without_gvl (and similar) functions extensions. Most notably, this fixes

This is a super quick announcement for a new Mongrel plugin called mongrel_console. It was inspired by a request from Tobias L?tke who wanted to tail out logs while Mongrel was running. What mongrel_console does is combine the Rails script/console with Mongrel so that you can control a mongrel server while using script/console. Sounds weird but it''s quite awesome for development

Hey Luis, Just implemented the first cut at a graceful stop setup. It seems to mostly work except for a few hicups here and there which I''ll test out. I''ve tested this under OSX and will test on the other platforms soon. To use it take a look at the examples/simpletest.rb and see how I setup an "INT" handler to call HttpServer.stop. Hopefully this will help with

Hi, I am using a railsapp to call an external app and print some barcode-labels. My problem is, after a while there seems to be a timeout. Then I need to stop the Mongrel-Server and restart it. Below you can see the error message, when i stop the server. Has somebody seen this before? Greetings, Oli C:\etikett>mongrel_rails start -d -e production ** WARNING: Win32 does not support daemon

Hello Folks, This is the long awaited (like 2 weeks) 0.3.12 release of Mongrel. This release has received heavier testing than previous releases and supports a whole raft of improvements to existing functionality plus some new stuff. For those not clued in, Mongrel is a web server written in (mostly) Ruby. Check the funny dogs and read the docs about it at http://mongrel.rubyforge.org/. The

Before anything else, let me state this: Of course it''s going to be PAINFULLY slow on MRI. That''s not the point :) I thought I''d try out writing out a Ruby version of the parser for the purposes of Rubinius. For those of you who aren''t aware, Ragel supports a goto-driven FSM on Rubinius by injecting assembly directly, and Rubinus head honcho guy Evan Phoenix

Hello all, For the last couple of days I was trying to get my Apache/mod_proxy/mongrel setup to limit the size of the request body. The setup is as follows: 1.) Apache acts as a reverse proxy by facilitating mod_rewrite and mod_proxy 2.) Requests for non-static files are passed on to a mongrel_cluster 3.) We use mongrel for our Ruby on Rails application Note that due to some restrictions we are

I got some advice from Rick last night and started coding this handler to allow for time-based secure downloading similar to mod_secdownload that lighttpd offers. I got most of the code in the handler worked out and packaged into a gem but am still having the following problems: 1) I have a configuration script as follows require ''mongrel'' config = Mongrel::Configurator.new

Would you bother to setup a fastcgi for a "intranet accessible" application that is like to get < 100 hits a day? David

Hi, I am trying to run Mongrel on win32 to serve an internal rails application. We are accessing legacy data, and some transactions can take 5 to 10 seconds. This is holding up every other request. The -n does not seem to be supported on Win32. Am I missing something, or should I look elsewhere to serve my Rails app on win32? Thanks, Walt -- No virus found in this outgoing message.

Hi, I found this article http://cyll.org/blog/tech/2006-08-09-themongrelcomet.html on mongrel and COMET very interesting. I ran the code, and it worked just as Christopher explained. The one thing I don''t understand is why mongrel can only handle 1 connection at a time. I thought that mongrel used a thread per connection. It appears that each registered handler can only handle 1

Hello! Run problems after upgrading to mongrel 1.0.3 from 1.0.1: # uname -sr FreeBSD 7.0-BETA1 # mongrel_rails start ** Starting Mongrel listening at :3000 ** Starting Rails with development environment... ** Rails loaded. ** Loading any Rails specific GemPlugins ** Signals ready. TERM => stop. USR2 => restart. INT => stop (no restart). ** Rails signals registered. HUP => reload

--- lib/unicorn/configurator.rb | 19 ++++++++++++++++--- lib/unicorn/http_server.rb | 3 +++ test/unit/test_configurator.rb | 8 ++++++++ 3 files changed, 27 insertions(+), 3 deletions(-) diff --git a/lib/unicorn/configurator.rb b/lib/unicorn/configurator.rb index 0d0eac7..a0ae576 100644 --- a/lib/unicorn/configurator.rb +++ b/lib/unicorn/configurator.rb @@ -441,9 +441,22 @@ class

This small patch extends configure_socket_options to support FreeBSD''s accf_http(9), which defers accept() until there''s a full HTTP request to read. Seems to work fine on 6.1-STABLE. DragonflyBSD should work too provided the /freebsd/ line is modified to match it. accf_http(9): http://www.freebsd.org/cgi/man.cgi?query=accf_http&sektion=9 -- Thomas