Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:77995 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 70363 invoked from network); 14 Oct 2014 13:47:09 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Oct 2014 13:47:09 -0000 Authentication-Results: pb1.pair.com smtp.mail=mike@mjdugan.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=mike@mjdugan.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain mjdugan.com from 209.85.216.172 cause and error) X-PHP-List-Original-Sender: mike@mjdugan.com X-Host-Fingerprint: 209.85.216.172 mail-qc0-f172.google.com Received: from [209.85.216.172] ([209.85.216.172:57715] helo=mail-qc0-f172.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 6F/59-26074-D592D345 for ; Tue, 14 Oct 2014 09:47:09 -0400 Received: by mail-qc0-f172.google.com with SMTP id o8so6738811qcw.31 for ; Tue, 14 Oct 2014 06:47:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:message-id:in-reply-to :references:subject:mime-version:content-type; bh=sT45xRjQN5Mf5JDcj04rEdfTmdNvK3gt92XID9fQDqg=; b=bHce5PU+7ampMfUwDVB2JGMNFUM5Hy8AjD8vnUAruh0qtA5ZHulO3YdW1kfwLe+Xap 2rvAG9BTVndVFs0UDVb8l2tUc0JZ5KiOo7riQCmkKV4GJFaNtPGPP7nfxSlQpMD0BkRu 2l5UHil4p+IEybANeHEw0aB8oplYFmP84cJrRdIHitND60JiqGWK9tsWWuKBX5KMABtF K3Kl2jSyknwqHV3Ks1OSG9VKzLbPUxv5rDkjlTzwrgYm1P3ReEsvdm6sykgX6na1bIge VPQIqo90+UorbEuZf5YeggeC//9xF/ez639+MVQSIN+kNGkDKXnJSETUVNuD9KZcWqYZ 9MqA== X-Gm-Message-State: ALoCoQkphxXxORoExT1ahSvJbhNpVZ6GdII2gkUH/VmR5Ce21NLZlpp2gFBsMW2c5WsU7VwOsGnN X-Received: by 10.224.130.198 with SMTP id u6mr8957002qas.99.1413294426778; Tue, 14 Oct 2014 06:47:06 -0700 (PDT) Received: from Mikes-iMac.local (c-71-200-126-32.hsd1.md.comcast.net. [71.200.126.32]) by mx.google.com with ESMTPSA id l2sm15485592qao.34.2014.10.14.06.47.06 for (version=SSLv3 cipher=RC4-SHA bits=128/128); Tue, 14 Oct 2014 06:47:06 -0700 (PDT) Date: Tue, 14 Oct 2014 09:47:01 -0400 To: Andrea Faulds , Kris Craig Cc: Andrey Andreev , PHP internals list Message-ID: In-Reply-To: References: <776669CE-9E8C-4069-9834-C7275CCA0EF4@ajf.me> X-Mailer: Airmail (249) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="543d2955_46e87ccd_12d" Subject: Re: [PHP-DEV] New globals for PUT and DELETE From: mike@mjdugan.com (Mike Dugan) --543d2955_46e87ccd_12d Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --=C2=A0 Mike Dugan mike=40mjdugan.com On October 14, 2014 at 9:42:47 AM, Kris Craig (kris.craig=40gmail.com) wr= ote: On Tue, Oct 14, 2014 at 6:25 AM, Andrea =46aulds wrote:=C2= =A0 >=C2=A0 > On 14 Oct 2014, at 14:23, Andrey Andreev wrote:=C2= =A0 >=C2=A0 > > That being said, from a purely semantic prospective, both =24=5FGET a= nd=C2=A0 > > =24=5FPOST should be tossed - yes. In reality, you can't do that beca= use=C2=A0 > > virtually all PHP applications use them. But this is no reason to add= =C2=A0 > > even more global vars with such misleading ... meanings.=C2=A0 >=C2=A0 > Let=E2=80=99s add =24=5FREQUEST=5FBODY and =24=5FQUERY=5FSTRING and mak= e them aliases of =24=5FGET=C2=A0 > and =24=5FPOST then. Because they=E2=80=99re aliases (by-reference supe= rglobals),=C2=A0 > there=E2=80=99s no additional memory consumption, but we finally have s= aner names.=C2=A0 > --=C2=A0 > Andrea =46aulds=C2=A0 > http://ajf.me/=C2=A0 >=C2=A0 >=C2=A0 Removing or renaming =24=5FGET and =24=5FPOST would also create confusion= and=C2=A0 almost certainly cause widespread BC breakage on a pretty massive scale.=C2= =A0 And there's really no gain to offset that. So that just leaves us with=C2= =A0 either continuing to have two REST methods but not the others or add a=C2= =A0 =24=5FPUT and a =24=5FDELETE, even if they just alias to php://input agai= n.=C2=A0 --Kris=C2=A0 How are these RESTful methods=3F =24=5FGET accepts query strings, that=E2= =80=99s not part of the spec for RESTful GET requests unless I missed som= ething. I also don=E2=80=99t see the worldwide breakage and confusion tha= t would be caused - no one is proposing to drop =24=5FGET and =24=5FPOST = but rather to create more semantic aliases for them. =E2=80=94 Mike Dugan mike=40mjdugan.com --543d2955_46e87ccd_12d--