On Fri, Jan 15, 2010 at 11:32 PM, Jonas Sicking <jonas@sicking.cc> wrote: > On Thu, Jan 14, 2010 at 11:58 PM, Darin Fisher <darin@chromium.org> wrote: > > I don't think we should worry about underlying file changes. > > If the app wants to cut a file into parts and copy them separately, then > > perhaps the app should first copy the file into a private area. (I'm > > presuming that one day, we'll have the concept of a chroot'd private file > > storage area for a web app.) > > I think we should avoid solutions that involve file locking since it is > bad > > for the user (loss of control) if their files are locked by the browser > on > > behalf of a web app. > > It might be reasonable, however, to lock a file while sending it. > > I largely agree. Though I think it'd be reasonable to lock the file > while reading it too. > Wouldn't that require OS support for mandatory locking? That is not normally available on Linux or Mac OS X. Rob -- "He was pierced for our transgressions, he was crushed for our iniquities; the punishment that brought us peace was upon him, and by his wounds we are healed. We all, like sheep, have gone astray, each of us has turned to his own way; and the LORD has laid on him the iniquity of us all." [Isaiah 53:5-6]
Received on Friday, 15 January 2010 11:18:21 UTC