Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69319
Return-Path: <peter.e.lind@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 10699 invoked from network); 24 Sep 2013 15:13:57 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 24 Sep 2013 15:13:57 -0000
Authentication-Results: pb1.pair.com smtp.mail=peter.e.lind@gmail.com; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=peter.e.lind@gmail.com; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.182 as permitted sender)
X-PHP-List-Original-Sender: peter.e.lind@gmail.com
X-Host-Fingerprint: 74.125.82.182 mail-we0-f182.google.com  
Received: from [74.125.82.182] ([74.125.82.182:44460] helo=mail-we0-f182.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 87/A1-01825-33CA1425 for <internals@lists.php.net>; Tue, 24 Sep 2013 11:13:57 -0400
Received: by mail-we0-f182.google.com with SMTP id q59so4787894wes.13
        for <internals@lists.php.net>; Tue, 24 Sep 2013 08:13:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc:content-type;
        bh=BOZUcoDcy8duBG5UUL7/O9oSOAJFTC9pxCB56gVVnYc=;
        b=nOlOGqJVNk2uarv+JLecNFG6GnRzEZnvDQ777SfHSXxrbCC3UB3fOCtX0A2tgXmpGq
         P8Cv4haHmzn0ZYjXZzSChG3SmpcIC73s7oprKq+NPsdtg0E4dmUpn8Tta0gRI0A6I3HF
         GSs2dw5tOIf3Xq+045pW/gSrcSX+OoFBIlkMchNr3oqWFmNfUXnvXeosCU+hfzbmQny8
         ETWaw8sssLsKboktAJQ0NdqyF/NZ0G+tqmD16uokU0mwBoyO1Gy6EZB84lfuXLEPhyla
         FmXyK9skPTZleI+5i17SQ+VUt5Ehpi8H2K/PnpVv+PehdeNyyVMSvpl+1tz0/8Z9Jn/b
         /NEw==
X-Received: by 10.180.182.15 with SMTP id ea15mr18452661wic.16.1380035626779;
 Tue, 24 Sep 2013 08:13:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.227.198.134 with HTTP; Tue, 24 Sep 2013 08:13:26 -0700 (PDT)
In-Reply-To: <CAH8Mpnk6By7E_xn2oXNyvdvKGq=7V-_KOp2Kam-Ltj8Bt4WrHg@mail.gmail.com>
References: <CAH8Mpnk6By7E_xn2oXNyvdvKGq=7V-_KOp2Kam-Ltj8Bt4WrHg@mail.gmail.com>
Date: Tue, 24 Sep 2013 17:13:26 +0200
Message-ID: <CAEU6NAct1X804x4oCja4p6epbnfjuaSR_P0pJL5WPG9HE+Qy2w@mail.gmail.com>
To: Daniel Lowrey <rdlowrey@gmail.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>, Ryan McCue <lists@rotorised.com>, 
	Tjerk Meesters <datibbaw@php.net>, catch.dave@gmail.com
Content-Type: multipart/alternative; boundary=047d7b62535a4fcd0204e7229536
Subject: Re: [PHP-DEV] Re: Parsing PUT data
From: peter.e.lind@gmail.com (Peter Lind)

--047d7b62535a4fcd0204e7229536
Content-Type: text/plain; charset=UTF-8

On 24 September 2013 16:59, Daniel Lowrey <rdlowrey@gmail.com> wrote:

> The bigger issue here is that the superglobals are a leaky abstraction. Any
> HTTP request method is allowed to have an entity body, so should we also
> create $_PATCH and $_PUT and $_ZANZIBAR to handle less-frequently used
> request methods? Where does it stop? This is the problem I see with all the
> requests to support for PUT similarly to POST. PHP web SAPIs support 95% of
> the HTTP use-cases people have, but the abstractions break down after that
> and continuously bolting on support for individual scenarios beyond that
> would be a mistake IMO.
>

Supporting the base set would not seem a bad idea, I'd say -
http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9

PUT is not exactly exotic, though it might not be as used as it could be -
however, with the focus on REST APIs that is changing. Your argument makes
good sense for random HTTP verbs - but suggesting we shouldn't support easy
access to the basic set because "where does it stop" is not a very good
argument, in my eyes.

Regards
Peter

<http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9>--
<hype>
WWW: plphp.dk / plind.dk
CV: careers.stackoverflow.com/peterlind
LinkedIn: plind
Twitter: kafe15
</hype>

--047d7b62535a4fcd0204e7229536--