Re: Build failure
| From: | Rob Richards | Date: | Tue, 17 Apr 2007 14:59:51 +0000 |
| Subject: | Re: Build failure | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-28889@lists.php.net to get a copy of this message | ||
Unless anyone sees a way to do this without adding the lock, I'd like to
commit this patch.
It adds a php_flock call only for windows. In doing so I got rid of the
win32/flock files and now compile with flock_compat from main.
Rob
Richard Quadling wrote:
> The testing I'm using is to launch multiple copies of the same PHP
> script simultaneously using php.exe (CLI mode). This could easily be
> multiple FastCGI scripts or multiple ISAPI threads.
>
> On 16/04/07, William A. Rowe, Jr. <wrowe@rowe-clan.net> wrote:
>> Richard Quadling wrote:
>> > So isn't locking the solution for Windows?
>>
>> If this is single writer process, even with multithreads - a mutex
>> is most efficient, otherwise with concurrent writer processes, file
>> locking makes the most sense.
>>
>> Bill
>>
>
>