Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:122046 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 25286 invoked from network); 26 Dec 2023 05:02:23 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 26 Dec 2023 05:02:23 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 50D1E18004E for ; Mon, 25 Dec 2023 21:02:44 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DMARC_MISSING,HTML_MESSAGE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE, SPF_NONE autolearn=no autolearn_force=no version=4.0.0 X-Spam-Virus: No X-Envelope-From: Received: from mail-yw1-f169.google.com (mail-yw1-f169.google.com [209.85.128.169]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Mon, 25 Dec 2023 21:02:43 -0800 (PST) Received: by mail-yw1-f169.google.com with SMTP id 00721157ae682-5eb072c0b69so12195767b3.0 for ; Mon, 25 Dec 2023 21:02:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=interi-co.20230601.gappssmtp.com; s=20230601; t=1703566937; x=1704171737; darn=lists.php.net; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=TnHdfDTTbzZf3cJBPU8QT+6MSX0fUriEFxztJg+ty8k=; b=o7KsNS1m5vMYC8rq9z+N3c+sruEyuY99Uy56FjbGW8ZOFqKi8mZzNk+CaeZI2Bj7u7 6APd1yAUDnmuT/oW21q+7fAe1LrJlyIGcYY3pNgM8mHuUUjNmWP0Pw0fM/WstMR73KLc F0ZWxoADU7SHfCoCZ6dbyqQ+C2MB4qGzw9+PFe8wSThtacbBLhQK7KjlYfvp+wFgsItZ 0QL4sv9AjXug3wMvAgs5ZfCtQJe4FC3Tiw4Lm1JKyyIW+zkPP0tdNoFqs9S5vssYt+mU jHq6qnm6UuJb7adKoGgI3q5qd2t62fa5zzcL27AebOQsE9cYNK8+MuFUUGRisdcaVCL1 8QcA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1703566937; x=1704171737; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=TnHdfDTTbzZf3cJBPU8QT+6MSX0fUriEFxztJg+ty8k=; b=OWmag7wVnOxBs5/OexmMTQxwy3jD29qF5DtKgsdNG/Q057mInZwLG1F0T5/zNZUsL6 LRmdqkGutzuo7KCxaA9pB7m8ZEMSjldtoHioo8vagL2WKXeW+igHqz+cKBXoU+Spqh9h pso9md3Kpefbhxk5h5YKrcG/6hTB+mG8nAOIQyHnIPK2Db/NjOBJhLPj8+07v3M7uUC8 zHRVjCqlRRwKNgzxm7+Jt9d42S7uCmQyXvWBdXvbVsiBf1Xs93OPDS7cqnxPpDrUu1cI Fa0aeMaQFDmyGwcOfiX4Giaxwo8fc2hAdiPLx7cOFZFvHKMF6pGt3zcMP34Gc2xYyN7A dkXw== X-Gm-Message-State: AOJu0YxLybeubOEK5kYo2oWqvN5TUHCcSvQOdrUqL6pLAhTsYkCSEZEz vSOGGyRR//c2iww6joRv2y0vQJWDWBsaZi1fU7cWoyzOa3ToLg== X-Google-Smtp-Source: AGHT+IEYTl7TGHZAcUz11EStBlPX3CHT5g/YpwjC2i1KkVEVKuiLQVcXETievo26I5dmH7vWPYyl0jniFLVxga4kZDA= X-Received: by 2002:a81:5b82:0:b0:5d7:1940:b36e with SMTP id p124-20020a815b82000000b005d71940b36emr4241050ywb.58.1703566937428; Mon, 25 Dec 2023 21:02:17 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Tue, 26 Dec 2023 14:02:05 +0900 Message-ID: To: Jordan LeDoux Cc: =?UTF-8?Q?K=C3=A9vin_Dunglas?= , internals@lists.php.net Content-Type: multipart/alternative; boundary="0000000000002824f2060d6296d7" Subject: Re: [PHP-DEV] RFC proposal: worker mode primitives for SAPIs From: alex.pravdin@interi.co (Alexander Pravdin) --0000000000002824f2060d6296d7 Content-Type: text/plain; charset="UTF-8" > > So you want to introduce a SAPI that doesn't work with any of the existing > HTTP solutions people use that only supports HTTP requests? Or am I > misunderstanding something? > > This sounds a bit like you want to merge in a tool that is designed for > your personal product directly into core. FrankenPHP may be incredible and > awesome, but the world runs on Apache and Nginx for HTTP requests. > > To be honest, after trying RoadRunner (an alternative to FrankenPHP), I'm using it for all my projects if the framework and packages have no issues with this execution model. Only old codebases with extensive usage of global variables and stateful services are at risk. If you stick with readonly classes and follow best DI practices, there will be minimum to no issues. Symfomy is actively propagating safe coding styles. So from my POV it is not a problem that a new execution model will be supported. If your code is not compatible - then this is your problem. It is normal that some code may not work properly in different modes. The fact that the world is running on Apache and Nginx doesn't mean this will be forever with no alternatives. The fact that there are multiple projects with the same goal shows that there is a big demand for PHP speedup. And there are no visible alternatives except a worker mode. IMO. --0000000000002824f2060d6296d7--