Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:81885 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 16499 invoked from network); 5 Feb 2015 09:14:20 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Feb 2015 09:14:20 -0000 Authentication-Results: pb1.pair.com header.from=mike.php.net@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=mike.php.net@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.176 as permitted sender) X-PHP-List-Original-Sender: mike.php.net@gmail.com X-Host-Fingerprint: 209.85.212.176 mail-wi0-f176.google.com Received: from [209.85.212.176] ([209.85.212.176:35301] helo=mail-wi0-f176.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 49/CB-51979-96433D45 for ; Thu, 05 Feb 2015 04:14:19 -0500 Received: by mail-wi0-f176.google.com with SMTP id bs8so37467143wib.3 for ; Thu, 05 Feb 2015 01:14:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=wvvFPzaY+1voSbon21Na2EFDUGFOYAjdYW2PzYcCVT4=; b=AxBFYesshfryhmfV5F8R4TPTbe15MOdSCrE8F3s1pVtqm/IWSW3nj0Arm/yDU3bv0s KotVFj4s/HpvHwNagDE+Y0EAWwC4S/bp4y1Kmj1eP5MifbZtnx6q2AkWY0Rcca77qfm4 0NU7OV6ZKI5cfFZtTXcI9kjOq8gQCaZKzp7yEYlPyHsKqGrc2bma3NLDv3F38hVHXBrt itqulMngx7av0TU2Efii0rkEr7yzOaGQtZWsiYwqbzQk4/J3ALzd7iAqMwPiH/3Q3kSg Soi6h2oGGd/weWv3zwmx3fqGmR+mvxG6dXn9UEhx230dQmacX9q8JqbBmZuENNMIC0vX YJUA== X-Received: by 10.180.37.33 with SMTP id v1mr55108495wij.76.1423127654170; Thu, 05 Feb 2015 01:14:14 -0800 (PST) Received: from [192.168.2.120] (89-104-28-113.customer.bnet.at. [89.104.28.113]) by mx.google.com with ESMTPSA id di11sm6935660wid.8.2015.02.05.01.14.13 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 05 Feb 2015 01:14:13 -0800 (PST) Sender: Michael Wallner Message-ID: <54D33464.7090009@php.net> Date: Thu, 05 Feb 2015 10:14:12 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Stanislav Malyshev , PHP Internals References: <54D217E7.8030407@php.net> <54D2AE91.8090800@gmail.com> <54D3271E.2080207@php.net> <54D32A38.9050004@gmail.com> <54D330C3.7030001@php.net> <54D331D3.5080809@gmail.com> In-Reply-To: <54D331D3.5080809@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Re: [RFC] [DISCUSSION] pecl_http From: mike@php.net (Michael Wallner) On 05/02/15 10:03, Stanislav Malyshev wrote: > Hi! > >> Yes, I mean $_POST (and $_FILES). It's been requested multiple times, >> but I know it's quite controversial. I think this approach is better >> than any other proposed yet (think $_PUT and stuff). > > You're building an OO next-generation API, why you still need $_PUT or > $_FILES or anything like that? Just make a nice OO API where the client > can request the data cleanly, and hide the details of where they come > from. Which would probably also make an added value of making these > things actually testable with some minimal API support, without messing > with superglobals and general extreme ugliness. > Because PHP soaks up all data on POST and leaves us without php://input, so on POST it would be PHP that decides what to happen, and on any other method it would be pecl/http. That seems to cry out loud for inconsistencies. Anyway, that feature is not of that huge practical use, that it deserves argumenting too long about it. I'll remove that section. -- Regards, Mike