WOMultipartFileIterator and 'wis' StreamActionRequestHandler
WOMultipartFileIterator and 'wis' StreamActionRequestHandler
- Subject: WOMultipartFileIterator and 'wis' StreamActionRequestHandler
- From: Jonathan Rochkind <email@hidden>
- Date: Wed, 06 Aug 2003 15:56:09 -0500
The "What's New in 5.2" document says:
"It is possible to get the raw data of a request as an InputStream (thus
avoiding the memory overhead), however, but this requires using the
StreamActionRequestHandler (wis) with a direct action."
However, consider the examples included in the FileUpload example project.
However, consider the examples included in the FileUpload examples project.
The "Direct Action Iterator Upload" example (DAUploadIteratorPage) has a
form which posts to a direct action, true. However, it does NOT use the
'wis' action handler. The direct action DOES use an InputStream to access
the form data---although now that I consider exact wording, it doesn't get
the entire WORequest data as a stream, just the file upload data itself.
Did I just answer my own question? You need to use the 'wis' handler only
when you want to get the entire HTTP request as an InputStream, rather than
using the WOMultipartFileIterator to get just the uploaded file content as
an InputStream?
So my actual questions are: What is the 'wis' handler for, exactly? When do
I need to use it? If I only need to use it when I want to get the entire
HTTP Request as a stream (but NOT when I only want to get the uploaded file
content as an InputStream).... why would I ever want to do this? What's the
point?
-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.