On Fri, Jan 16, 2009 at 3:53 PM, Karsten Dambekalns <kars...@typo3.org> wrote: > Hi Pierre. > > On 16.01.2009 14:33 Uhr, Pierre Joye wrote: >>> >>> While NTFS supports path lengths of up to 32k characters, >> >> By the way, this limit is approximative. > > In what way? > >> There is no plan yet to increase this value. The main problem is that >> the maximum length of a path is volume dependent, not system >> dependent. > > Right. One FAT volume could wreck it all. > >> To support longer path, it would mean to check the volume information >> for each file operation (once per volume, cache it and reuse it) as >> well as using dymamic allocation for for the filename itself, in many >> places. I'm not sure it is worth the effort. > > Sounds bad. I just cannot believe it is still easily possible to "break" a > machine by simply using FAT32 under Vista. Phew. > >> You can use a hash as filename, as a temporary workaround. > > Well, not really. Our names include some information, so hashing isn't > really an option. For now we'll probably just skip supporting Windows.
The problem is exactly the same on any OS, only the size varies. The limit is not higher either. What do you use as naming for your entries? -- Pierre http://blog.thepimp.net | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
