Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78012 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 96390 invoked from network); 14 Oct 2014 14:21:38 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Oct 2014 14:21:38 -0000 Authentication-Results: pb1.pair.com smtp.mail=ben@benramsey.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=ben@benramsey.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain benramsey.com from 209.85.216.170 cause and error) X-PHP-List-Original-Sender: ben@benramsey.com X-Host-Fingerprint: 209.85.216.170 mail-qc0-f170.google.com Received: from [209.85.216.170] ([209.85.216.170:57681] helo=mail-qc0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FD/B2-18603-1713D345 for ; Tue, 14 Oct 2014 10:21:37 -0400 Received: by mail-qc0-f170.google.com with SMTP id m20so6850489qcx.1 for ; Tue, 14 Oct 2014 07:21:34 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=yVih3hi0a8/XCZZ+N/w/bfmRW2h5yu0X/bROL1bSJT4=; b=Q3jYm7UONEMGNa01SNhsIzQJ26b5pu2FFu1gjI63+dvv1v5gdmtBs/zkz6z/4FfEst 3VUIg6ygSVMilvbIfE2B8RoxfqLC8dFyJgdcwddDmfMdPiafJt3CjD2hNy6vEjMzZXt6 edqMAsyIHNU40FPHFjN9v+FRZdNBBaYXmL85NMjMsYXrnVYm8KNVy7doN5xRESSaE98X WADQqZnKaf3ymf2eXMJrzmDFLcJaGyNsyLzmEMj1z8SOt5gm00IlHcZN1MMlAKviPnq4 wQNaH1OVpaV6GqbyN9qeEVmCs8Ls9uaIQx0e6G5u2pc+9Wt/CgTxK6WIf3Mxnk54qpbp oS/Q== X-Gm-Message-State: ALoCoQmZ+YXOG6g/Db2jCRPw0y+NrFPXlPlIJtOhib8AcsP+Ctgv8EvrcKY6SRgOeIAqIfHXNcEz X-Received: by 10.224.129.195 with SMTP id p3mr4876qas.66.1413296494119; Tue, 14 Oct 2014 07:21:34 -0700 (PDT) Received: from [10.0.0.70] (c-68-52-228-18.hsd1.tn.comcast.net. [68.52.228.18]) by mx.google.com with ESMTPSA id l2sm15558942qao.34.2014.10.14.07.21.33 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 14 Oct 2014 07:21:33 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) In-Reply-To: Date: Tue, 14 Oct 2014 09:21:32 -0500 Cc: Andrea Faulds , Chris Wright , Kris Craig , Andrey Andreev , PHP internals list Content-Transfer-Encoding: quoted-printable Message-ID: References: <776669CE-9E8C-4069-9834-C7275CCA0EF4@ajf.me> <4240E494-94E6-4FC9-BB84-C30FFA69129C@benramsey.com> <69EB8F97-7CFC-44E0-8B2D-C2230ADAC87F@ajf.me> To: Mike Dugan X-Mailer: Apple Mail (2.1878.6) Subject: Re: [PHP-DEV] New globals for PUT and DELETE From: ben@benramsey.com (Ben Ramsey) On Oct 14, 2014, at 9:08 AM, Mike Dugan wrote: > On October 14, 2014 at 10:04:00 AM, Andrea Faulds (ajf@ajf.me) wrote: >>=20 >>=20 >> So $_QUERY and $_FORM, then. That sounds about right.=20 >>=20 >=20 > Did I just name a global variable? W00t! >=20 > Anyhow, yeah neither one is technically 100% correct, but like Andrea = said, the majority of usage will be from forms and query strings with = parameters. At any rate, it=92s makes more sense semantically in the = context of what the var actually contains than $_GET and $_POST ever = will. >=20 +1 I=92m cool with $_QUERY and $_FORM. They make much more sense and don=92t = try to use HTTP verbs, which can confuse the content and semantics of = the data they contain. Plus, they would just alias $_GET and $_POST, = respectively, right? -Ben