WOMultipartIterator
WOMultipartIterator
- Subject: WOMultipartIterator
- From: Jonathan Rochkind <email@hidden>
- Date: Thu, 07 Aug 2003 13:16:59 -0500
I am trying to use WOMultipartIterator in a direct action (well, really in
a custom request handler action, but it behaves like a direct action for
these purposes). For a file upload.
I am confused as to what I have to do to avoid reading the entire file into
memory. I've read over the documentation, and the "What's New in 5.2"
document many many times, but I'm still confused--it's complicated.
I have a form that contains a file upload. It also contains other form
key/values BEFORE the file upload. I want to read these key/values before
I deal with the file upload. I also, of course, want to make sure the
entire file upload is NEVER read into memory, for instance as part of the
WORequest.
How do I access these non-file form values? Can I use formValueForKey,
without worrying this cause my file to be read into memory? Can I call
formValueForKey on my key values multiple times, without worrying this will
cause my file to be read into memory? Can I call formValueKeys() without
causing my file to be read into memory? Am I better off just using the
WOMultipartIterator iterator to get my non-file form values, like I'm going
to use it later to get my file form values? Am I even _allowed_ to combine
a WOMultipartIterator with calls to formValueForKey/formValueKeys for the
same WORequest?
Also, headerValueForKey() and headerKeys()... I'm okay calling these as
much as I want however I want, without worrying about it causing the
uploaded file to be read into memory, right? For instance, to get the
content-length header.
--Jonathan
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.