Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121411
Message-ID: <af8bad31-a636-4dd8-b0ad-191ee110c52d@bastelstu.be>
Date: Wed, 18 Oct 2023 19:09:44 +0200
MIME-Version: 1.0
Content-Language: en-US
To: Derick Rethans <derick@php.net>
Cc: Ilija Tovilo <tovilo.ilija@gmail.com>,
 PHP internals <internals@lists.php.net>
References: <CAPyj-LD0EDYUZSOM=P9doSZRJ8LipSKKUSBHxV-bRbCV1QsYtQ@mail.gmail.com>
 <6fccfe47-21ac-fa5b-e52e-28064f26125b@bastelstu.be>
 <91b89c73-03f8-31df-cfab-84009b3d3bce@php.net>
In-Reply-To: <91b89c73-03f8-31df-cfab-84009b3d3bce@php.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [RFC][Under discussion] RFC1867 for non-POST HTTP verbs
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=)

Hi

On 10/18/23 18:07, Derick Rethans wrote:
>> Regarding the cleanup of the files, perhaps the files could be read into a
>> `php://temp` stream
>> (https://www.php.net/manual/en/wrappers.php.php#wrappers.php.memory)?
> 
> I don't think that reading potentially large files into memory is a
> great idea. It is precisely because of the memory issue that PHP's
> existing POST handler writes files to disk, instead of leaving their
> content available through an entry in $_FILES.

To clarify: `php://temp` spills over to disk at a certain size (2 MB by 
default).

Best regards
Tim Düsterhus