W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2011

[whatwg] Intent of the FileSystem API

From: Tatham Oddie <tatham@oddie.com.au>
Date: Wed, 2 Mar 2011 01:31:55 +0000
Message-ID: <913F550AEE09194E9D4B5BFB9CF3FD4B0D20C1@EXMBX07.netplexity.local>
Glenn,

That's an XP path you've provided.

On Vista or 7 it'd be:

	C:\Users\tatham.oddie\AppData\Local\Google\Chrome\User Data\Default\Storage

Microsoft explicitly did work in Vista to reduce the lengths of those base paths.

Now, the Google component of the path is actually the longer part.


--
Tatham Oddie
au mob: +61 414 275 989, us cell: +1 213 280 3556, skype: tathamoddie
If you?re printing this email, you?re doing it wrong. This is a computer, not a typewriter.

-----Original Message-----
From: whatwg-bounces@lists.whatwg.org [mailto:whatwg-bounces@lists.whatwg.org] On Behalf Of Glenn Maynard
Sent: Monday, 28 February 2011 4:39 PM
To: Eric Uhrhane
Cc: whatwg at whatwg.org
Subject: Re: [whatwg] Intent of the FileSystem API

On Mon, Feb 28, 2011 at 7:10 PM, Eric Uhrhane <ericu at google.com> wrote:

> Our current implementation on Windows uses the standard API calls that 
> limit paths to 256 characters long.  If your profile directory is 
> deeply nested [e.g. because you have a really long username], code
>

Worse, the profile directory is deeply nested all by itself--it looks like the typical location for this data would be something like:

C:\Documents and Settings\Glenn\Local Settings\Application Data\Google\Chrome\User Data\Default\Storage

That's past 100 characters already.

--
Glenn Maynard
Received on Tuesday, 1 March 2011 17:31:55 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:31 UTC