rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / Atom feed
From: Daniel Abrahamsson <hamsson@gmail.com>
To: rack-devel@googlegroups.com
Subject: Does Rack-servers block until the whole request body has been read?
Date: Wed, 13 Apr 2011 00:17:41 -0700 (PDT)	[thread overview]
Message-ID: <31236863.1318.1302679061651.JavaMail.geo-discussion-forums@yqlq3> (raw)

[-- Attachment #1: Type: text/plain, Size: 997 bytes --]

Hi,

I am working on a server that deals with large file uploads (currently built 
upon Rails, with a Metal taking care of the uploads). According to the 
rack-specification:
"... handler developers must buffer the input data into some rewindable 
object if the underlying input stream is not rewindable".

For Passenger and Mongrel, this means a temp file is created for the request 
(at least for requests as big as those I am dealing with).

Now, my question is, does Rack wait until all data from the client has been 
read to a tempfile before passing on control to the Rack app (in this case, 
Rails)? Or does it pass on control directly, and block if the application 
reads data faster than the client is sending it?

After some initial testing, it appears to me that the former is the case. 
Can anyone give me advice on how to test this? Perhaps it depends on the web 
server used? Perhaps on the framework?

Thank you in advance for any advance or clarification on this matter.

//Daniel

[-- Attachment #2: Type: text/html, Size: 1030 bytes --]

             reply	other threads:[~2011-04-25  5:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-13  7:17 Daniel Abrahamsson [this message]
2011-04-25 14:26 ` Does Rack-servers block until the whole request body has been read? Joshua Ballanco
2011-04-26  1:16 ` Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://groups.google.com/group/rack-devel

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=31236863.1318.1302679061651.JavaMail.geo-discussion-forums@yqlq3 \
    --to=rack-devel@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).