AW: "Choosing" the WOWorkerThread that executes the request...
AW: "Choosing" the WOWorkerThread that executes the request...
- Subject: AW: "Choosing" the WOWorkerThread that executes the request...
- From: Helge Staedtler <email@hidden>
- Date: Tue, 16 Aug 2005 18:03:17 +0200
This may be the case. I have bound following bindings for my fileupload:
--- HTML ---
<WEBOBJECT NAME=Upload1></WEBOBJECT>
--- WOD ---
Upload1: WOFileUpload {
filePath = currentResource.fileNameFromUploadingClient;
size = "20";
name = currentResource.uniqueId;
outputStream = currentResource.os;
bufferSize = 32;
}
In my java code i then have a look at the WOMultipartIterator which comes in
during takeValuesFromRequest. I then do some checking about the
contentLengthRemaining.
--- JAVA ---
contentLengthRemaining = mpi.contentLengthRemaining()
Do you think there is something essential missing? Even if I upload e.g. 60
MB of data, my progess is starting to show up after 30 seconds or so on a
LAN; then already 3 MB are there and the progress is so fast it gets
finished in 5 more seconds. This cannnot be possible if it would stream
continually.
The documentation says the adaptor will turn the upload into "real"
streaming starting at 1MB uploadsize, so...
Regards,
Helge
Am 16.08.2005 1:56 Uhr schrieb "Chuck Hill" unter
<email@hidden>:
> It works in deployment for me. Are you sure you have the
> WOFileUpload bindings set correctly for streaming?
>
> Chuck
--
Helge Städtler
- Expect and Respect.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden