Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:108783 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 46078 invoked from network); 27 Feb 2020 18:39:18 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 27 Feb 2020 18:39:18 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 5613D180551 for ; Thu, 27 Feb 2020 08:57:16 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-il1-f171.google.com (mail-il1-f171.google.com [209.85.166.171]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Thu, 27 Feb 2020 08:57:15 -0800 (PST) Received: by mail-il1-f171.google.com with SMTP id x2so150018ila.9 for ; Thu, 27 Feb 2020 08:57:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=qeCU0tUEYchxYxyFU55c6uEnGq008wT4Su0ht6Cy0KA=; b=l4Yir3z/OZa3rJEW5zPTy5CkLR6HUo6n3sCSUOoOgWifMuHUEeVBJEWIawlJwGtrjt r1A5pITtc8zRHP77PRO6GGIIaMLwQMGyoBh7T3weiAYUKpWdjpPGnUDGZfjBrzKNT8KL OHMX2eICO4iJXrSipvIBK9UXzf2I1CPh8gxCi2JUMAwLQt676Was7zRc0Xb3yphJmieF sJ/Lfa9LU/E00jOxtJldn/ie31Qf+Ud5y3plIZDh23wO80f9BBIVkJouniJ0eAR/MH15 ZdQomkanMWSN8th5elQgV1xqDuSxtkubikAHf0dIvunkOdaHaPR8TO6uHUmQNjIQs3QT +siA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=qeCU0tUEYchxYxyFU55c6uEnGq008wT4Su0ht6Cy0KA=; b=sqdciz2hu+H5Vkuu8DCPr+9TZfQt71MCQY5MclDrBWTQ5vpu/+G8nsNOV/XMBrsDZt YCJXsPidA4NPpeZ+Dtn0XhlJlgXZCLUb6RLqBFrYraLHqEKJaxs6ANs+wEVkH5WDcxEG PvzvcbHiZvWMPvMyQKqYC7Nhy0iVvg2e5or/ikT55dz3HtEcN3S+EiJZlapAsovq8V8N kaIUGri4aK6WK4UYsYn/Bt+iRl34tXR0hq3j/8lLred5yOMIF55nfSC1Ien/3zSKAcp+ FM1iqyUD+4L79OryX+dm09bDe74H3RTRIzkeHv8zqSqSn1YMwDI/OnRo/RoOp33irDAk zkTQ== X-Gm-Message-State: APjAAAW2yvqRp6n6DTHuLy9iimtLk5ZBl+aQ+0U0qZhiDDnr/WGg6M0K Q7hv4bb9nsxizx+aUIob5R4epcQ8P+9foXMiVMukgg== X-Google-Smtp-Source: APXvYqx2I0g+U3/pn7SdjqZ74b77dfYZaPR9cXw8IfOxX934+HaejZlDBjx8gLJX2nPJPWvnFXFtMk9R8WX77nWt17s= X-Received: by 2002:a92:91c7:: with SMTP id e68mr200015ill.161.1582822634969; Thu, 27 Feb 2020 08:57:14 -0800 (PST) MIME-Version: 1.0 References: <50BD013E-CF72-414C-BBC0-A7A2E45CBDDB@pmjones.io> <5904137.fSVIMsojiJ@mcmic-probook> <3DDBFBA4-8D3A-46C5-9A10-B093A5E2386B@pmjones.io> <54493258-B52E-442A-A11D-82E1D4C7DE5E@gmail.com> <8264F6CF-AD55-41E2-9F5A-DAE8942E2B79@pmjones.io> <1BF3D29A-04C6-4A82-9216-EAE991A38916@pmjones.io> <10388b3a-3402-a6dc-3837-b03d735edf46@gmail.com> <5ec7b4a7-508b-270b-916f-0504a116196c@gmail.com> <30112AFF-38F9-44D4-9D2F-03A32019764F@pmjones.io> <27F45990-E3AE-4A77-85EC-A2CA1EAC73E4@pmjones.io> <012FB9B5-B2F6-4C2D-9F12-5F5BAC508742@pmjones.io> In-Reply-To: <012FB9B5-B2F6-4C2D-9F12-5F5BAC508742@pmjones.io> Date: Thu, 27 Feb 2020 16:57:03 +0000 Message-ID: To: php internals Content-Type: multipart/alternative; boundary="000000000000e65e24059f919cce" Subject: Re: [PHP-DEV] RFC: Server-Side Request and Response Objects (v2) From: rowan.collins@gmail.com (Rowan Tommins) --000000000000e65e24059f919cce Content-Type: text/plain; charset="UTF-8" On Thu, 27 Feb 2020 at 15:55, Paul M. Jones wrote: > > Why not hope that ReactPHP and others will want to use this object, > > precisely because it avoids them having to roll their own implementations > > of things? > > Like I said earlier: if React ends up wanting to use ext/request, with its > tradeoffs, of course I would think that's great. But if they want to keep > using what they have already, with its own tradeoffs, that's great too. > This is one place our attitudes differ: if I was proposing something like this to be included in every copy of PHP, I'd actively want people to use it, and consider that a measure of success; you seem to be happy to just put it out there and see. As such, I perhaps place greater value on functionality that would make it more attractive, and less value on matching what we already have. > This is very similar to what I'm saying: to use your phrasing, I opine it > is better to "trivially wrap" the existing PHP functionality as part of a > separate RFC, rather than try to embed it in ServerRequest (exposed or > otherwise). > That's not really the same, no. I am saying that once you have the parsing functionality somewhere in userland, whether it's inside ServerRequest or its own function doesn't matter, you could still use it to delete 300+ lines of code from ReactPHP. That's a reason to add it *as soon as possible*, even if in an ideal world it would be implemented in a slightly different place, or two different places, or whatever. Regards, -- Rowan Tommins [IMSoP] --000000000000e65e24059f919cce--