Re: Cache_Lite 1.0 ?

From: Date: Fri, 08 Nov 2002 08:03:03 +0000
Subject: Re: Cache_Lite 1.0 ?
References: 1 2 3 4  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-10608@lists.php.net to get a copy of this message
On Fri, 2002-11-08 at 08:55, Fabien MARTY wrote: > > I don't have to append anything else to this list. And filelocking is > > somehow better than before, isn't it? If just see this log-entry: > > Mon Oct 21 13:10:18 2002 (2 weeks, 3 days ago) > > adding fileLocking to file's constuctor. this allows users to use file > > locking in the file container without modifying the original php > > code.--dviner > > Indeed, fileLocking isn't enough to prevent from cache corruption. Because > when you remove a file, you can't use fileLocking. Moreover, it doesn't work > with distributed file system (NFS...) and with multithread servers... > > So to prevent from cache corruption, the best way is a md5 (or crc32...) > hash embedded in the cache file. Have a look at 'Cache_Lite / docs / > technical' file for more details. Ok, thanks for your reply. Maybe we should implement this in PEAR::Cache some day to get real file corruption prevention... But me personally has absolutely no time to implement, so it's very low in my TODO list :( > Yet, there is another way (which sounds very interesting), it's the use of > Direct I/O support (has to be compiled into PHP (--enable-dio)). It's an > idea of Patrick O'Lone. I have put it in the TODO file of Cache_Lite. Never worked with dio but sounds interesting chregu

« previous php.pear.dev (#10608) next »