Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:122045 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 21105 invoked from network); 26 Dec 2023 03:18:34 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 26 Dec 2023 03:18:34 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 234F7180053 for ; Mon, 25 Dec 2023 19:18:58 -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.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,DMARC_PASS,FREEMAIL_FROM, HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=4.0.0 X-Spam-Virus: No X-Envelope-From: Received: from mail-oa1-f45.google.com (mail-oa1-f45.google.com [209.85.160.45]) (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 19:18:57 -0800 (PST) Received: by mail-oa1-f45.google.com with SMTP id 586e51a60fabf-204301f2934so2878810fac.1 for ; Mon, 25 Dec 2023 19:18:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1703560711; x=1704165511; 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=nnNGer9+XnwAXz9s+HjOpaPbr5BeS5YEyE490iBfxVo=; b=VSrDbXFygmPTQb3gdFFt+v+hqMInVVljNzhSGfyMM/kM8SahAT3iHfwiDR6ZgJBfhc NVnSq8eLsNLCM7AemYO5JF4FP5BAqMFMhbifS9Ym/nkhOBs0uoq14snbPbGLYxTXJrM/ Ve4n5kNaxw7HW11sQwMcyty5HvX83Xh5bJTessUljpAm8yVvG2GMV++3sxUp6zBek9G1 sg33/d10SIDj85T3VJTWUzWUQuYL4+ucVF/IT7vVqiE4wV0GLIlyjR8rSToV4Je35qlg 75ADM+e8JykGF5fidpbaHryds2VMlhlOj+HkxhMAYDl0oxi5bFRBR7E4i8yccESAfzwp +P9w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1703560711; x=1704165511; 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=nnNGer9+XnwAXz9s+HjOpaPbr5BeS5YEyE490iBfxVo=; b=f6rU9Gb9uIPUD4sGEk6vPaN8dZa/KXu4PBpXxs88qHyENugWCR44tDs6vRldw+TXB8 WdIOQwq6Uqaa5rIzKL3+NLbnNkkwJ3nhanz/n0gOedHtMgDcIZW7mG3HmmKt1EBIMa9D nEBBxgtWk2xcq2HZLI2HOcIfyMIE5r+Jr8EfNWLHjZujLSTdnvrMTE28+jNmXW2O3YPh YaWWy4lON7eUyD+KqBkXjH54IgXxUm/4QM11Cit89JlwX8GAXwfqWWeVAykUyybcjlmq iq59L+3F/1oIbFMRcRrd6bo9wuueWcEVXmL7kUh/TANCRn8CzpiEEpH2FYABCneI8B5X 7COA== X-Gm-Message-State: AOJu0YyTD7P87zeJqs++7o6Lq4OCDNM7MMUnGXxeEQ99qXMGB2+cMXiB pMI5C8lgwXLYYzhuva4OPhKpegKrSCxOyb1M/aQ= X-Google-Smtp-Source: AGHT+IGwugzMCx4GRqiWdkDlwzqNzUJVvMOc6x/DXdbHufjSRMuNYc0z+ntQLMqjTU5doxe0ExICyyLs5KimvOSdBG0= X-Received: by 2002:a05:6870:51cf:b0:203:df0b:1702 with SMTP id b15-20020a05687051cf00b00203df0b1702mr7636789oaj.65.1703560711523; Mon, 25 Dec 2023 19:18:31 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Tue, 26 Dec 2023 10:18:18 +0700 Message-ID: To: Jordan LeDoux Cc: =?UTF-8?Q?K=C3=A9vin_Dunglas?= , PHP internals Content-Type: multipart/alternative; boundary="000000000000105226060d612338" Subject: Re: [PHP-DEV] RFC proposal: worker mode primitives for SAPIs From: pierre.php@gmail.com (Pierre Joye) --000000000000105226060d612338 Content-Type: text/plain; charset="UTF-8" Hello, On Tue, Dec 26, 2023, 1:56 AM Jordan LeDoux wrote: > > 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. The world was running on cgi when php was created and a few years after. Then the world was running on threads/apache. Then it ran in fcgi and finally fcgi fpm for the last few years. Other languages support this since quite some time. Projects like reactphp, swoole and the likes provide userland versions of it and the benefits are clear. They even worked together recently to get a common core. Many (large) projects out there already support FrankenPHP, the needs are there. FrankenPhp and a worker mode go beyond the classical php usages we had. Desktop applications or IoT are getting more common (see laravel's nativephp f.e.). I have done something similar for one of our products using embedded sapi but how it is done using frankenphp would be an order of magnitude better. Having the complex parts in the core us a good start to experiment, adapt. Later a core sapi may be added, we cannot know without trying and let the community uses it. best, Pierre --000000000000105226060d612338--