Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:120644 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 64308 invoked from network); 20 Jun 2023 11:06:33 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 20 Jun 2023 11:06:33 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id E41661804BE for ; Tue, 20 Jun 2023 04:06:32 -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=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE 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-wm1-f52.google.com (mail-wm1-f52.google.com [209.85.128.52]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Tue, 20 Jun 2023 04:06:32 -0700 (PDT) Received: by mail-wm1-f52.google.com with SMTP id 5b1f17b1804b1-3f9b627c1b8so10358335e9.1 for ; Tue, 20 Jun 2023 04:06:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1687259191; x=1689851191; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=UO+m4eAnFh8KuMuYYSzQBZGQDWg/jsuiSIBakZ8vFBw=; b=V9JhmcNcUFI1gH4CKOzlhFVM0uHltCIOnFnIkllNZPZqfRYM4lvXQua/k94GEM4SsJ aQ4T/ix9sDEGQ0SAW3y7lwAwVhD/J+FSkbpA0GxTuy7wIFzw8eBs7oggxucs8e/PCHsc zh1ylFyx7AjFW81v0zxUB7IfvECEEjNNe2DXlvQTi7bOWi4M2tG8ZJ2kAIMZL1z1Xq5T 0WEalwShfq+LnO1gL4EgkekNQyXyuwRB+FapeEvjkd0+xrjTzP6lPc1VLqEAXLYy9qgW FGuGSLy0QIX7W7TJSo39VVPTqojNzQWHNaLTcrLBnDv2BnVcHpCKAKyJXho/fb3qJPR/ 6Hug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687259191; x=1689851191; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=UO+m4eAnFh8KuMuYYSzQBZGQDWg/jsuiSIBakZ8vFBw=; b=Cn0AirSFb2gMWHdbOK1/kJV6q50Vlutk1hKQYa6wqqhjhgNnZIgXDa2AyrmrlkbwX0 vYDXoymfeGpfFZF4hVE8svvGhkhOhWshWhUs+kLA0dsoONSZyKAJHop2nwy3JEf8gMot njWNn5lbv+t7KmGB8KOYEtPhxyQRWQIIaNEU71VidjAImRPO7Ys5T3IvBqzJBqI7XwFV A2FvyGW0eo0UUKikt9ZV8U7IXTojGFN0ddo6foA3mYz1lt62AVcTKyohlQGrh9XS3eox b76e4rFI3NKgjeYUN/8ay+0eKuBVtg2tE6LygIwku6HB8zP0H9qq2pbe+ywtKHYDydQ1 OMHA== X-Gm-Message-State: AC+VfDzyY5pEpdZ+0UYz+Vy96PeEPyErQBDiY9FZ+CQmk3e87vUyYmM+ MglUrct0g4pWBf/Jr1dldEpbCMnlR/eVbiCto9Mkhmy4vVA= X-Google-Smtp-Source: ACHHUZ76UFgJ+lXjhBdx4nkgS8WUGmpiqkd7QBxIafVLqhfJjyPfoB3Vbxr+pUhr4BT5saY4Y4x4+cs2vpL3hiFc9mI= X-Received: by 2002:a1c:e909:0:b0:3f6:a65:6ff3 with SMTP id q9-20020a1ce909000000b003f60a656ff3mr10543878wmc.32.1687259190464; Tue, 20 Jun 2023 04:06:30 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Tue, 20 Jun 2023 12:06:18 +0100 Message-ID: To: PHP internals Content-Type: multipart/alternative; boundary="000000000000b1138105fe8da44b" Subject: Re: [PHP-DEV] RFC1867 (multipart/form-data) PUT requests From: rowan.collins@gmail.com (Rowan Tommins) --000000000000b1138105fe8da44b Content-Type: text/plain; charset="UTF-8" On Tue, 20 Jun 2023 at 10:25, Ilija Tovilo wrote: > Introduce a new function (currently named populate_post_data()) to > read the input stream and populate the $_POST and $_FILES > superglobals. > My initial instinct was to discuss how this could be made more flexible in terms of input and output; but looking at how simple the implementation is, this seems like a really quick win, and anything else can be future scope. To bikeshed the name a bit: * We should probably avoid the word "post"; although it populates $_POST, that's really misnamed anyway, what we're really talking about is "form data" * Even if there isn't a current category prefix where it belongs, it should probably follow the "category_specific" naming scheme * We might in future add some related functions, such as returning the data rather than populating globals How about "request_form_populate_globals"? Regards, -- Rowan Tommins [IMSoP] --000000000000b1138105fe8da44b--