
On Fri, Jan 6, 2012 at 11:03 AM, Felipe Almeida Lessa
On Fri, Jan 6, 2012 at 1:45 AM, Michael Snoyman
wrote: Actually, the application can have full control over this, by either ignoring the request body entirely (Warp will essentially stream it to /dev/null) or throwing an exception.
On this move to conduit, I'd like to see some sort of a Source of POST parameters on Yesod. AFAIK, currently the only pretty API is the one that puts the whole request into memory. What do you think about it, Michael? Something that spits out a stream of
data StreamPostParam = NewParam {- info about the param -} Data ByteString
I think you're talking about an enhancement to the Network.Wai.Parse API. I actually think it's already pretty close to this, we likely need to just expose the internals a bit more. I'm definitely in favor, and I'll add an issue (under the yesod repo, simply because more people stay up-to-date on those issues, though it should technically go under wai). Michael