From: Brian Lopez <seniorlopez@gmail.com>
To: rack-devel@googlegroups.com
Subject: Re: Adding #size to rack.input
Date: Mon, 22 Feb 2010 14:59:08 -0800 [thread overview]
Message-ID: <35FEBDD2-7B7B-4B24-9835-0B494D3F5069@gmail.com> (raw)
In-Reply-To: <63d3361b-53d7-4f4a-ac49-27ec3cdd2525@f42g2000yqn.googlegroups.com>
What does this mean for streaming requests?
-brianmario
On Feb 22, 2010, at 2:52 PM, Hongli Lai wrote:
> On Feb 22, 11:46 pm, Ryan Tomayko <r...@tomayko.com> wrote:
>> On Mon, Feb 22, 2010 at 3:14 AM, Hongli Lai wrote:
>>> Hi Ryan.
>>
>>> Rack.input is already required to be rewindable, meaning the input has
>>> to be backed by a file or a StringIO at some point. It should be
>>> trivial for pretty much all Rack web servers to implement #size. Do
>>> you have any objections against including #size in the spec?
>>
>>> With kind regards,
>>> Hongli Lai
>>
>> That's a good point. Any objections to adding #size to the SPEC and
>> Rack::RewindableInput? I'd be happy to put the patches together.
>
> It should be noted that this request came from Chad Fowler who
> encountered the problem in the Gemcutter website. The existing code
> already assumes that #size is available, which is the case for e.g.
> Thin which exposes a StringIO or Tempfile as rack.input.
next prev parent reply other threads:[~2010-02-22 22:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-22 22:46 Adding #size to rack.input Ryan Tomayko
2010-02-22 22:52 ` Hongli Lai
2010-02-22 22:59 ` Brian Lopez [this message]
2010-02-23 2:30 ` James Tucker
2010-02-23 3:33 ` Ryan Tomayko
2010-02-23 10:29 ` James Tucker
2010-02-23 23:30 ` Hongli Lai
2010-02-24 2:57 ` Yehuda Katz
2010-02-24 14:24 ` James Tucker
2010-02-26 8:05 ` Charles Oliver Nutter
2010-02-26 10:49 ` Christian Neukirchen
2010-02-27 0:33 ` Eric Wong
2010-02-27 2:01 ` Yehuda Katz
2010-02-28 15:19 ` Hongli Lai
2010-03-01 1:56 ` Charles Oliver Nutter
2010-03-11 23:56 ` Graham
2010-03-08 18:40 ` Kyle Drake
2010-02-26 19:53 ` Nick Sieger
2010-02-26 21:20 ` Yehuda Katz
2010-02-22 23:01 ` Magnus Holm
2010-02-23 23:29 ` Hongli Lai
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=35FEBDD2-7B7B-4B24-9835-0B494D3F5069@gmail.com \
--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).