Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110347
MIME-Version: 1.0
References: <CA+p1FabH1rL48z=QNP8324WNmaJvAN=skfWi7b9NCnpU5MVHag@mail.gmail.com>
In-Reply-To: <CA+p1FabH1rL48z=QNP8324WNmaJvAN=skfWi7b9NCnpU5MVHag@mail.gmail.com>
Date: Wed, 3 Jun 2020 12:16:35 +0200
Message-ID: <CAF+90c_+q4kQf31BHE-48ggZH4kUMRtZXsE99QOY96wjUFxDrg@mail.gmail.com>
To: David Gebler <davidgebler@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000009733ce05a72b53c1"
Subject: Re: [PHP-DEV] RFC proposal: fsync support for file resources
From: nikita.ppv@gmail.com (Nikita Popov)

--0000000000009733ce05a72b53c1
Content-Type: text/plain; charset="UTF-8"

On Mon, Jun 1, 2020 at 6:57 PM David Gebler <davidgebler@gmail.com> wrote:

> Exactly as the subject says, I would like to propose an RFC for adding an
> fsync() function for file resources, which would in essence be a thin
> wrapper around C's fsync on UNIX systems and _commit on Windows.
>
> It seems to me an odd oversight that this has never been implemented in PHP
> and means PHP has no way to perform durable file write operations, making
> it inherently unsuitable for any systems requiring more intensive I/O,
> mission critical logs, auditing, etc.
>
> I am not really a C programmer and I have been able to implement a simple
> working prototype of this as a compiled extension in merely a few hours, so
> I'm sure it wouldn't be difficult to bring in to the language core where
> the functionality really belongs.
>
> Every other major programming language otherwise comparable to PHP in
> features supports a way of providing durability.
>
> Thanks.
>

No objections from my side. I assume you'd want to add both fsync() and
fdatasync()?

I think all it takes for this one is a PR...

Regards,
Nikita

--0000000000009733ce05a72b53c1--