It's just an open item, and one that I had hoped I could contribute on. If
you have some ideas on restructuring the param handling I can take it from
there. No rush.

Derek

On Tue, Jun 30, 2009 at 3:33 PM, David Pollak <feeder.of.the.be...@gmail.com
> wrote:

> What kind of priority is this issue?  I think I can abstract things in such
> a way that it works correctly, but it'll take a couple of days.
>
> On Tue, Jun 30, 2009 at 2:08 PM, Derek Chen-Becker 
> <dchenbec...@gmail.com>wrote:
>
>> Well, as usual something that seemed simple at first glance is now looking
>> somewhat complex. I'm thinking of reworking the fileUpload handling to allow
>> a user to register either a (String, String, Array[Byte]) ⇒ Any or (String,
>> String, InputStream) ⇒ Any function, which would then be executed during
>> request processing. The issue is that form field processing (ParamHolders)
>> takes place in Req, before LiftSession has been set up, and the act of
>> parsing the request for form data, particularly for large upload streams
>> (the target of these changes) precludes holding on to any data for later
>> processing (the servlet container cannot be expected to hold the entire
>> request in memory). On the other hand, users should reasonably expect that
>> their form handling functions are stateful, so I'm trying to think of some
>> way to meet in the middle on form processing. Ideas?
>>
>> Derek
>>
>>
>>
>
>
> --
> Lift, the simply functional web framework http://liftweb.net
> Beginning Scala http://www.apress.com/book/view/1430219890
> Follow me: http://twitter.com/dpp
> Git some: http://github.com/dpp
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to