Re: [Seaside] Re: Re: [squeak-dev] [Q] File Upload/Download Server, Comanche or Swazoo

> 10 GB is massive. There are whole lot of 32bit integers that can
> overflow and a lot of other things that can go wrong at any stage
> including the browser and Apache.
>
>> My current idea is that I should create module(?) for Comanche or Swazoo for File
>> Upload (this just process multipart/form request for file upload with additional
>> parameters) and small web application or module for processing download url.(This
>> might be possible with Seaside with RESTable URL support or simple module).
>
> I only tried the upload streaming for Kom on localhost. While it could
> handle largish files (40 MB) it wasn't able to get close to 400 MB. So
> Kom might not be your tool. I have not seen an upload streaming API
> for Swazoo (which doesn't mean it's not there). Squeak might not be
> the best tool for the job where. HTTP might not be as well.

>> See this example from http://www.swazoo.org/streaming.html:
>>
>> Site>>answerTo: aHTTPRequest
>>  | stream |
>>  aHTTPRequest
>>    postDataAt: 'file'
>>    beforeStreamingDo: [:datum |
>>      stream := (SpFilename named: datum filename) writeStream.
>>      datum writeStream: stream].
>>
>>  aHTTPRequest ensureFullRead. "to be sure streaming occurs"
>>  stream close.           "mandatory, to close open stream! "
>>
>>  ^HTTPResponse ok
>>
>>
>> In that example we open a file named as the original file, which  is sent in
>> request as post data, just before a file content.
>>
>> I hope that helps
>
> Nope sorry. See the attached code. Your example and the attachment
> work only if there is an upload filed with the name 'file'. That's the
> only upload filed that will be streamed. That's why the attached code
> breaks. If you change the name of the upload field to 'file' then the
> code breaks somewhere in MultiByteFileStream (Squeak 3.9 Mac VM).