Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:77997 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 73956 invoked from network); 14 Oct 2014 13:50:04 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Oct 2014 13:50:04 -0000 Authentication-Results: pb1.pair.com header.from=are.you.winning@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=are.you.winning@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.48 as permitted sender) X-PHP-List-Original-Sender: are.you.winning@gmail.com X-Host-Fingerprint: 209.85.192.48 mail-qg0-f48.google.com Received: from [209.85.192.48] ([209.85.192.48:64037] helo=mail-qg0-f48.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 6B/3A-26074-B0A2D345 for ; Tue, 14 Oct 2014 09:50:04 -0400 Received: by mail-qg0-f48.google.com with SMTP id i50so8341174qgf.21 for ; Tue, 14 Oct 2014 06:50:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=ZbfWgS6HyV7Ub6nQQIX+iYgy3oW9RDYjYdz7MthUHdw=; b=H4TuSUjiNRsQn6I9/7wqGEEmhKdD5uwksRnKqZMPKm2rvQzibeAcRL510RO+dKhPYu LbXEZRM5+pMbb4wUxKtHGPn+vDYuAEMdLSJa2d9f1q7zOJR8lLA1eaAPlGcUS4bQGlp0 BMN00+hFrPLg9yzNNF+V3VLUC8A6L0+IlQ6z3SlK27H6tnNRaNbV6e3kIO5KCDY7ROgB 9+6Ggeu4mkwHM2GdGIaiZJo7NPp0mfV6/kampZJA4pdBWcQSwzv0vRJ89fLI5N5/n8+J 5XjmjimJSAFcOqTUCJUyeI7axx3E71N3wkQzQ4XovXyE66QQ3dQ1qSXHOjBF9HImCcIf bjIQ== MIME-Version: 1.0 X-Received: by 10.224.64.71 with SMTP id d7mr9546699qai.16.1413294601437; Tue, 14 Oct 2014 06:50:01 -0700 (PDT) Sender: are.you.winning@gmail.com Received: by 10.141.28.193 with HTTP; Tue, 14 Oct 2014 06:50:01 -0700 (PDT) In-Reply-To: References: <776669CE-9E8C-4069-9834-C7275CCA0EF4@ajf.me> <8CB055D4-F164-4DF3-B019-684BAE7E016E@ajf.me> Date: Tue, 14 Oct 2014 14:50:01 +0100 X-Google-Sender-Auth: R5PNQd7Fq4UHWxNk37s8wc1rXFk Message-ID: To: Kris Craig Cc: Mike Dugan , Andrea Faulds , Kristopher , PHP internals list , Andrey Andreev Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] New globals for PUT and DELETE From: cw@daverandom.com (Chris Wright) On 14 October 2014 14:46, Kris Craig wrote: > On Tue, Oct 14, 2014 at 6:41 AM, Mike Dugan wrote: > >> >> On October 14, 2014 at 9:31:15 AM, Andrea Faulds (ajf@ajf.me) wrote: >> >> >> On 14 Oct 2014, at 14:27, Kristopher wrote: >> >> > $_HTTP_REQUEST_BODY and $_HTTP_QUERY_STRING for nostalgia's sake. >> >> Ew, non-superglobals. >> >> But $_REQUEST_BODY and $_QUERY_STRING are a bit lengthy. Perhaps $_QUERY >> (for $_GET) and $_BODY (for $_POST)? Then the variable set finally makes >> sense, but isn=E2=80=99t too long: >> >> * $_QUERY - query string parameters >> * $_BODY - request body parameters >> * $_REQUEST - query string and request body parameters >> >> Makes more sense than $_GET and $_POST. >> >> Any objections? >> >> -- >> Andrea Faulds >> http://ajf.me/ >> >> >> +1 for this. This would hopefully also eliminate the confusion for new >> developers (or not-so-new developers) who don=E2=80=99t quite understand= that $_GET >> and $_POST don=E2=80=99t strictly relate to their HTTP verbs of the same= name. >> >> -- >> >> Mike Dugan >> >> mike@mjdugan.com >> > > That could work, though the BC breakage will be extreme. I'm not sure if > that's worth it even in a major version increment. On the other hand, > making $_PUT and $_DELETE available wouldn't break anything and wouldn't > require re-training for devs. ...but is also the wrong solution. It's not scalable, and the only sensible way to implement them would be as aliases of $_POST, because they would contain the same data. How does this fundamentally differ from $_BODY (or whatever)?