Hi Sirius,
I use a a direct action. I began following this approach because I
am dealing with large files and had no desire for them to be in
memory. In the WOMultipartIterator docs it says: "The InputStream
subclass is a WOFormDataInpuStream and can be used to stream large
file uploads to disk."
To test, create a multipart form with a file upload in an HTML file
and set the form action to a direct action on your webobjects app. I
can send you some sample code if you'd like.
:)
asa
On Apr 21, 2008, at 10:43 AM, sirius black wrote:
I like the idea of this approach, but maybe I'm not understanding
you completely. If I change my html to not use WOFileUpload and
instead just upload like a normal file-upload:
Browse file:
<input name="fileName" type="file">
<br><webobject name="SubmitButton"/>
-------------------------------------------------------------------
SubmitButton: WOSubmitButton {
action = submit;
value = "Upload File";
}
Then it seems like I'm still reading in all the data before I even
get to my takeValuesFromRequest. In fact when I get to larger files
(~ 500MB -> 1.0GB) I don't even get to the takeValuesFromRequest and
something else goes wonky.
Is this how you meant to implement this? Or am I missing another
web-objecty way to grab the file name information.
Thanks,
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
