similar to: Passing from data via POST

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

Hello I''ve a client which send this request to a mongrel HTTPHandler : res=Net::HTTP.post_form(URI.parse(''http://localhost:3000/test''),{"a"=>1,"b"=>2}) But in the handler I can''t read the parameters one by one, I can read the entire String only : class Serveur class MyHandler < Mongrel::HttpHandler def process(req, resp)

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

Hi. I am currently learning Ruby and writing an app that simply uses Mongrel''s HttpHandler class to create simple ruby servlets. At the end I have been using code similar to the example in simpletest.rb: h = Mongrel::HttpServer.new("0.0.0.0", "3000") h.register("/test", SimpleHandler.new) #h.register("/files",

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,

Hi, I''m trying to do a very simple slide_down effect with RJS templates. Basically a user selects a check box and a text box slides down. This works great in firefox, but causes IE to crash. The text box appears and slides down. Then the browser crashes. the in the partial is <div id=''forklift_div''> <label for=''incident_forklift''>Was

I started actually using the upload progress handler, and noticed it was leaking memory over time. Looking at the code, I noticed that cancelled uploads weren''t being cleaned up. I bugged Zed about adding a request_abort callback to handlers, but I found a simple way to monkey patch that in: # config/mongrel_upload_progress.conf # yes, this file is being used with -S meaning

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

Hi, I''m trying to write a file upload monitor for mongrel that uses juggernaut to alert the browser of a change. I''m writing a plugin that uses Mongrel::HttpHandlerPlugin but it looks like the only method that gets called is process and that is only when the upload has finished. I''m setting the following: @request_notify = true But I am still only getting process to

hi Geoffrey, Since you are saying it happens on all types of volumes, lets do the following: 1) Create a dist-repl volume 2) Set the options etc you need. 3) enable gluster volume profile using "gluster volume profile <volname> start" 4) run the work load 5) give output of "gluster volume profile <volname> info" Repeat the steps above on new and old

Hi All I''m getting the following very strange Ajax error and I''ve searched Google, this group and various other places to no avail. So I''m desperately hoping someone here can help. Whenever I try to execute any Ajax call whether as a form request or a link_to_remote link I get the following error: ------------------- FORM REQUEST ------------------- [2007-01-21

Okay, I've traced it to a bug in configparser, which on my python 2.7.4 system is a backport of configparser from python 3. Here is a clean patch that works around the problem. Geoffrey On Wed, Nov 6, 2013 at 10:24 AM, Geoffrey Irving <irving at naml.us> wrote: > LLVM builds with me on the release_33 branch, but fails on trunk. I > bisected the problem to this commit: > >

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.

Dear all, I have a crash test cluster where i?ve tested the new version of GlusterFS (v3.7) before upgrading my HPC cluster in production. But? all my tests show me very very low performances. For my benches, as you can read below, I do some actions (untar, du, find, tar, rm) with linux kernel sources, dropping cache, each on distributed, replicated, distributed-replicated, single (single

Hey all I am working with a technology standard (specific to the commercial print industry) by which each element within the workflow has bi- directional HTTP messaging. As each side needs a http server, I thought I could either: a) use a gem plugin to modify the behavior of mongrel b) subclass Mongrel::HttpHandler In short, its xml messaging between two points; each with a HTTP client

When I''ve got a view example like this: 1: response.should have_tag "fieldset#children" do 2: with_tag "child" 3: end If it can''t find ''child'', the error seems to come back as my_spec.rb:1 instead of my_spec.rb:2. Has anyone else experienced this? I just spent a while tracking down what I assumed was a problem in my have_tag only to

So, having gotten a story (i.e. Story Runner) working (runs in NetBeans and using ''ruby path/to/story.rb''), I''m looking to see how I''d integrate that with our build. Am I right in assuming that there''s no Rake integration yet, or a report? I couldn''t see any. As far as I can see, "rake spec" doesn''t run or report on my

I was planning on using a fixture within a description that didn''t modify the fixture, so I put it in a before(:all) block: describe "Customer", "xml" do fixtures :customers before(:all) do one = customers(:one) end # ... As a result, I got this message: 1) NoMethodError in ''Customer xml before(:all)'' You have a nil object when you

False Positives I just discovered how easy it was to create a false positive when I, trying my first RSpec test, did this: ob.should eql?(''foo'') instead of: ob.should eql(''foo'') or: ob.should == ''foo'' As far as I can see, this is roughly equivalent to: ob.should false Neither eql?(''foo'') nor false causes the spec

Hi everyone, Is there an easy way to parse multipart form requests from within a Mongrel::HttpHandler subclass or do I need to break out RFC 2388 and a bunch of regexps? Thanks, Mark -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20061221/9e756aa8/attachment.html