[Zope] LocalFS - large files / broken connections

[David Siedband]

It's on a Sun e3000 running FreeBSD.

Sorry for not mentioning that in my original post.
--
David


On Saturday, August 16, 2003, at 11:54 AM, Jaroslav Lukesh wrote:

>> Odesílatel: David Siedband <david at calteg.org>
>> I'm using LocalFS as a repository for uploading files.  Many files are
>> relatively large, perhaps in the 10-20 Meg range.
>>
>> Is the file cached by Zope and then written to the filesystem all at
>> once or is it written to the filesystem in incrementally?  From the
>> product code below, it looks like it it writing directly to the path
>> location...
>>
>> What happens if someone is uploading a file and their net connection 
>> is
>> broken?  How would this be handled?  Could this result in a partial
>> file being cached somewhere that needs to be purged or perhaps a write
>> process that needs to be killed off?
>
> Hi David,
>
> do you use windows, true? Use linux, not windows! I have no problems 
> under
> Linux, but few unresolved problems under windows (same version of zope,
> same products, same dats.fs) in windows.
>
> Regards JL.
>
> _______________________________________________
> Zope maillist  -  Zope at zope.org
> http://mail.zope.org/mailman/listinfo/zope
> **   No cross posts or HTML encoding!  **
> (Related lists -
>  http://mail.zope.org/mailman/listinfo/zope-announce
>  http://mail.zope.org/mailman/listinfo/zope-dev )
>