Re: New draft of FileSystem API posted

Hi Eric, On Jul 8, 2010, at 03:50 , Eric Uhrhane wrote: Robin: - data stored there by the application should not be deleted by the UA without user intervention, UA should require permission from the user, The application may of course delete it at will - these sound like real conformance

Re: New draft of FileSystem API posted

Hi Eric, Thanks for your reply. Actually after sending that email I had started to think that caching isFile / isDirectory information in memory would be ok if user could get an informative error code when an entry becomes stale -- and seems like that's the case. So I'm almost convinced :) One

Re: New draft of FileSystem API posted

On Fri, Aug 13, 2010 at 10:58 AM, Eric Uhrhane er...@google.com wrote: On Thu, Aug 12, 2010 at 11:08 PM, Kinuko Yasuda kin...@chromium.org wrote: Hi Eric, Thanks for your reply. Actually after sending that email I had started to think that caching isFile / isDirectory information in

Re: New draft of FileSystem API posted

Fixed. While I was in there, I deleted an unused class [FileSystemsCallback] and changed the boolean persistent parameter [from requestFileSystem and requestFileSystemSync] to be a more-general flag, to allow for future expansion. Eric On Fri, Aug 13, 2010 at 11:23 AM, Kinuko Yasuda

Re: New draft of FileSystem API posted

My apologies for the slow response; I'm now back from my vacation. On Tue, Jul 20, 2010 at 6:27 PM, Kinuko Yasuda kin...@google.com wrote: Hi Eric, Thanks for brushing up the draft. We had some internal discussion about the API details and came up with a question regarding is{File,Directory}

Re: New draft of FileSystem API posted

Hi Eric, Thanks for brushing up the draft. We had some internal discussion about the API details and came up with a question regarding is{File,Directory} attributes of Entry interface. It seems like user agent needs to be able to tell if a given entry is file or directory synchronously (or from

New draft of FileSystem API posted

I've posted a new draft of File API: Directories and System [1]. In this draft I've rolled in quite a bit of feedback that I received since first posting it on DAP--many apologies for the delay. This is the first draft produced since we agreed to move this spec from DAP to WebApps; I hope those

<    1   2