[whatwg] Intent of the FileSystem API
tatham at oddie.com.au
Tue Mar 1 17:31:55 PST 2011
That's an XP path you've provided.
On Vista or 7 it'd be:
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.
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.
From: whatwg-bounces at lists.whatwg.org [mailto:whatwg-bounces at 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.
More information about the whatwg