Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:1263 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 1512 invoked by uid 1007); 5 May 2003 11:30:20 -0000 Message-ID: <20030505113019.1510.qmail@pb1.pair.com> To: internals@lists.php.net Date: Mon, 05 May 2003 21:30:56 +1000 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 References: <1051831866.2944.10.camel@hemna.uh.nu> <20030505110212.72298.qmail@pb1.pair.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 203.37.117.98 Subject: Re: [PHP-DEV] xmldoc() takes ages >>> thread safety. From: tk.lists@fastmail.fm (Terence) Sascha Schumann wrote: >>I'm wandering if it is neccesary to use flock() on ALL filesystem >>interactions in a web based (multi-threaded) application. > > > flock and fcntl predate the multi-threaded approach on Unix > and as such they have process granularity, i.e. they won't > help in multi-threaded environments. > > - Sascha OK. Does this mean that there is no way to avoid dirty read/writes without telling the web server to limit everything to one process?