[tahoe-dev] [Python-Dev] PEP 383 update: utf8b is now the error handler

David-Sarah Hopwood david-sarah at jacaranda.org
Thu May 7 19:17:34 PDT 2009


David-Sarah Hopwood wrote:
> Glenn Linderman wrote:
>> Any such escaping scheme like this could possibly run into length limits 
>> on the names, some discussion about that issue should be included in 
>> such proposals.
> 
> This was mentioned in my proposal:
> 
> # - whenever a Tahoe filename is converted to a name for a
> #   particular filesystem, if the result is too long for
> #   that filesystem, then fail the operation.
> 
> There is little else that can be done: as you say, *any* escaping scheme
> (including one using UTF-8B or private-use characters) might run into a
> length limit for a particular filesystem. A filename that has no need
> for escaping could also run into a length limit shorter than that of
> Tahoe.

More precisely, filesystem length limits can be on the filename, the path,
and/or the number of path components.

(The length limits on Windows, even just for NTFS filesystems, are an
absolute mess, depending on what API is used and whether the path
starts with "\\?\". See
<http://msdn.microsoft.com/en-us/library/aa365247.aspx> for the full
horror of it.)

-- 
David-Sarah Hopwood ⚥



More information about the tahoe-dev mailing list