Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:99915 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 82887 invoked from network); 18 Jul 2017 19:11:12 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Jul 2017 19:11:12 -0000 Authentication-Results: pb1.pair.com smtp.mail=lists@rhsoft.net; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=lists@rhsoft.net; sender-id=pass Received-SPF: pass (pb1.pair.com: domain rhsoft.net designates 91.118.73.15 as permitted sender) X-PHP-List-Original-Sender: lists@rhsoft.net X-Host-Fingerprint: 91.118.73.15 mail.thelounge.net Received: from [91.118.73.15] ([91.118.73.15:46935] helo=mail.thelounge.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 51/AE-02884-F4D5E695 for ; Tue, 18 Jul 2017 15:11:11 -0400 Received: from srv-rhsoft.rhsoft.net (Authenticated sender: h.reindl@thelounge.net) by mail.thelounge.net (THELOUNGE MTA) with ESMTPSA id 3xBqWZ1MF6zXMT for ; Tue, 18 Jul 2017 21:11:06 +0200 (CEST) To: PHP internals References: <64.32.02884.7983D695@pb1.pair.com> <86.8B.02884.8D93E695@pb1.pair.com> <387c1b9c-f738-5b28-0ed1-31b80d8bffb8@rhsoft.net> Message-ID: Date: Tue, 18 Jul 2017 21:11:05 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: de-CH Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] http_cookie_set and http_cookie_remove From: lists@rhsoft.net ("lists@rhsoft.net") Am 18.07.2017 um 21:02 schrieb Michael Morris: > > > On Tue, Jul 18, 2017 at 2:56 PM, lists@rhsoft.net > > > wrote: > > > > Am 18.07.2017 um 20:39 schrieb Michael Morris: > > Personally, I no longer directly use these calls, preferring > instead to use > Symfony's HTTP foundation classes. Those in turn are, I > understand, in the > process of being converted to implement the common interface > outlined here: > http://www.php-fig.org/psr/psr-7/ > I would be much more > interested in > seeing a bare bones implementation of that agreed on standard in the > language core then seeing something entirely new, especially a > band aid > solution > > > but why do you do this? > > > Because I want to be done in a matter of hours or at most days instead > of a matter of weeks or months. I've been down the "roll your own" road > many times. It usually isn't worth it it is when done right it takes me 20 seonds to deplay updates on several hosts with hundrests of instances - you just need to do it *one* time right and no: it won't save you days or even hours when you wrap *everything* in some framework call when a single native function line can do the same with hundret times less costs