Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:42661 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 61686 invoked from network); 16 Jan 2009 16:03:12 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Jan 2009 16:03:12 -0000 Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 72.14.220.159 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 72.14.220.159 fg-out-1718.google.com Received: from [72.14.220.159] ([72.14.220.159:21450] helo=fg-out-1718.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 77/27-27029-FBFA0794 for ; Fri, 16 Jan 2009 11:03:11 -0500 Received: by fg-out-1718.google.com with SMTP id 16so743998fgg.23 for ; Fri, 16 Jan 2009 08:03:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=J3pi2EJrtxt75LF2Yr/CWN6FxhojwL7h1cXCtKj/r64=; b=sxcXTVeJ4u1gKm5qc2GwEJvQCum+qTHrlZ4GmOLxYAZyXsWk46UZrT5M3eFrf2soLL COYBU6mh81q913IcOEydUKhON9GmNvRbHzsIdyiAm6HCjkzlm+bEXH0FCd39Vjt83y0/ 8JrHL6nK5kdOfm6MDdmeIK5dHgyGMYBwKDVI8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=dP/0a+8qRJ9S8CiSOD8+MHsxUMxmS9w8ZEsR+2f56mSNMKIY0moN7+kAQxrNRzfN2c Od5jRWtcZPOV7YlIVlqmlufl5Y6ag5UxmZ4EsjIKIpXqGgVHSmCGhPG+z6OKE3VA3Sgy 3TnSz1+fzWzMDBS5xZ6z4OKWvDtlvDAW50RTM= MIME-Version: 1.0 Received: by 10.86.95.20 with SMTP id s20mr116316fgb.39.1232121788585; Fri, 16 Jan 2009 08:03:08 -0800 (PST) In-Reply-To: <8C.85.27029.97F90794@pb1.pair.com> References: <8C.85.27029.97F90794@pb1.pair.com> Date: Fri, 16 Jan 2009 17:03:08 +0100 Message-ID: To: Karsten Dambekalns Cc: internals@lists.php.net Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Path length for files on NTFS From: pierre.php@gmail.com (Pierre Joye) On Fri, Jan 16, 2009 at 3:53 PM, Karsten Dambekalns 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