Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:115845 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 61025 invoked from network); 26 Aug 2021 04:13:56 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 26 Aug 2021 04:13:56 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id CBAB91804BE for ; Wed, 25 Aug 2021 21:48:15 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM,FREEMAIL_REPLY,HTML_MESSAGE,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_PASS,WEIRD_PORT autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-qt1-f174.google.com (mail-qt1-f174.google.com [209.85.160.174]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Wed, 25 Aug 2021 21:48:15 -0700 (PDT) Received: by mail-qt1-f174.google.com with SMTP id x5so1456726qtq.13 for ; Wed, 25 Aug 2021 21:48:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=YHGwbgpCiXIoZj0ijaSxl4ji9nxQaj1cyP4xKp9ROEg=; b=Gj4m8EuwYdEvEmZjI2No2nBTDw4hMtYRRlzpnUmug5JmIZPwL3e5NtoJxcW0sOx1wc 8tt4lBCCaGYEUdq+jU4FJBx/yAuSt9GP4IO374b/TDJIP4rHhGjKH+EevxB43b2J0gmL JFyCjlNDWEKIvuI9abWEBT7XIkclp5p1oMHMkm/56T4Smf+pFDRxIXLwaK4IelLbH82Q WLB1nVOpOQfAD6kfUgYIaK2O8Xii/le3cSWD9jS+WTxZLZLcy9iQNE3EhfBSpCjs4Bco yKnJK8aYiofn0fWbs9/ac3Xep2JZ4wL0i13cVjv8LOeShX65EBZPjQZ64Fhh/QowMhSp ldNg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=YHGwbgpCiXIoZj0ijaSxl4ji9nxQaj1cyP4xKp9ROEg=; b=ZL+fT0uMubrrPBN6lIM6QWuVNrDKSacx+Z9qUMPri9m8eZnpXaHP/4YVHbAuRTCq+j ZDwIhbfPEyBRkUw50wP8ISowzdSfgVPC/jjsW0xFusy5K6xoQWE3a2Emj/BlKz2taTGx KdD4WfsVoQQ+Mi4zUMaUAnxoqkWrpsvPp/XXdAjrxPK++zG51LDXFD6eMNNoEde4tvAa sjVXGf14k1XwrCGnfqfUbXgXurVAUA7v/aU8L/N9NOuJQLxqKlMrLpLi1c81BuY7ytGp mCcSjRYzsSR3Rg/5Y4kuo1uo1YpENPNiSAtn6Vs/H8ktfHAkUrYZ8zbMDqyhVtMqD4k1 k0+g== X-Gm-Message-State: AOAM533wFW2hsQJk+Qri12ZS3YB+MJitttjuqArBrtpKgFta2ACqoRGz J7kiun1SODi62CBY03nLx+sfqyKKGg6qUWudoxw= X-Google-Smtp-Source: ABdhPJxt7piTp9dPKvAyquPWZ+gqBJU8Hb7znLUkVa+iA2APODHq7lytWNKO+HuaNOAUXnZUv4BopGc5WeraRMbgEaw= X-Received: by 2002:a05:622a:356:: with SMTP id r22mr1508970qtw.161.1629953293118; Wed, 25 Aug 2021 21:48:13 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Wed, 25 Aug 2021 21:48:01 -0700 Message-ID: To: Pierre Joye Cc: Derick Rethans , PHP internals , Nicolas Grekas , Marco Pivetta , Deleu Content-Type: multipart/alternative; boundary="000000000000096f3605ca6f1308" Subject: Re: [PHP-DEV] Guidelines for RFC post feature-freeze From: guest271314@gmail.com (guest271314) --000000000000096f3605ca6f1308 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi. I read the requirements to ask for a feature. I have been following your list. Interesting. I just want to do this https://web.dev/fetch-upload-streaming/, https://glitch.com/edit/#!/fetch-request-stream. This works as expected with a Blob or File: fetch('index.php', { headers: { 'Content-Type': 'text/plain' }, allowHTTP1ForStreamingUpload: true, method: 'post', body: new ReadableStream({ start(c) { c.enqueue(new Blob([123])); c.close(); }, }), }) .then((r) =3D> r.text()) .then(console.log) .catch(console.error); At HTML document: POST http://localhost:8000/index.php net::ERR_FAILED TypeError: Failed to fetch PHP built-in server: Invalid request (Unexpected EOF) in PHP. I tried to unsubscribe from your list, got mail error. If you find the time, can you kindly direct me to where this is possible in PHP, or if you find the use case a positive addition to PHP, perhaps work towards implementing it. Kindly unsubscribe me from your mailing list. You folks are involved. Carry on. On Wed, Aug 25, 2021 at 8:19 PM Pierre Joye wrote: > Hi, > > On Thu, Aug 26, 2021, 1:09 AM Derick Rethans wrote: > > > On 25 August 2021 18:34:18 BST, Nicolas Grekas < > > nicolas.grekas+php@gmail.com> wrote: > > >Le mer. 25 ao=C3=BBt 2021 =C3=A0 19:32, Marco Pivetta a > =C3=A9crit > > : > > , > > > > > >> On Wed, Aug 25, 2021 at 7:30 PM Nicolas Grekas < > > >> nicolas.grekas+php@gmail.com> wrote: > > >> > > >>> I would welcome a new RFC to clarify what is allowed during the > feature > > >>> freeze. > > >>> > > >> > > >> See https://en.wikipedia.org/wiki/Freeze_(software_engineering) > > >> > > > > > > > > >Can you please let me know how that helps? > > > > Maybe you didn't read the post, but generally a feature freeze in > software > > development is some time were no new features are added so a code base > can > > stabilise. This usually happens just before a release. These periods ar= e > > really important as they allow for 3rd party tools, documentation, etc = to > > be ready when a piece of software is released. On top of that, this > period > > can also be used by users to make sure everything is stable, and that > there > > are no critical bugs. > > > > > I suppose everyone knows what a freeze is. > > Also the issue here is not about the PHP features freeze period (RMs do a > good job here to announce and update it well on advance). > > It is about amending RFC for completeness (or whatever other reasons). I > can understand a RFC author does not want it for some random extension > being added. However I do see challenges when it comes to the very PHP co= re > syntax and languages. > > As we expected many years ago when we introduced the RFC process, I do se= e > a need to slightly clarify how the core of the PHP language is handled. N= ot > to block any changez but really to make it clear, what we can accept, vet= o > possible (it is now), etc. > > For the discussion about whether the null intersection was a feature or a > refinement, I would suggest just to ignore it. too late too little. > > best, > Pierre > > > > --000000000000096f3605ca6f1308--