Re: http_cookie_set and http_cookie_remove
| From: | lists@rhsoft.net | Date: | Tue, 18 Jul 2017 19:11:05 +0000 |
| Subject: | Re: http_cookie_set and http_cookie_remove | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-99915@lists.php.net to get a copy of this message | ||
Am 18.07.2017 um 21:02 schrieb Michael Morris:
On Tue, Jul 18, 2017 at 2:56 PM, lists@rhsoft.net <mailto:lists@rhsoft.net> <lists@rhsoft.net <mailto:lists@rhsoft.net>> wrote: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 costsAm 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/ <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 solutionbut 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