Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:108248 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 55991 invoked from network); 26 Jan 2020 00:25:59 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 26 Jan 2020 00:25:59 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 30CFB1804D1 for ; Sat, 25 Jan 2020 14:35:44 -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,RCVD_IN_DNSWL_NONE, SPF_HELO_PASS,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS24940 116.202.0.0/16 X-Spam-Virus: No X-Envelope-From: Received: from outbound.soverin.net (outbound.soverin.net [116.202.65.215]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits)) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Sat, 25 Jan 2020 14:35:43 -0800 (PST) Received: from smtp.freedom.nl (unknown [10.10.3.36]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by outbound.soverin.net (Postfix) with ESMTPS id D8DFD60959; Sat, 25 Jan 2020 22:35:41 +0000 (UTC) Received: from smtp.freedom.nl (smtp.freedom.nl [116.202.65.211]) by soverin.net DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=freedom.nl; s=default; t=1579991741; bh=cHma99PCUQHvplIjLOPxIJHMdjoKFuB00A/oducmEAQ=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=LlFOQFr1Fb9TM68/OfSr9iuAWNucvdc9YWPtfu5mszVvjpQxbLfOXsDJpEW4BH0cd JbvpC0NGhdqsEmrBzCKi1WvpO+GgMmhkRPB/2jBq100Ec+i+ZVdkqjl2FjM7Q63hXL uMdgvuSVZmtbscppcd6XWOA9jnFuf4CBwRZLjUbc= DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=freedom.nl; s=default; t=1579991741; bh=cHma99PCUQHvplIjLOPxIJHMdjoKFuB00A/oducmEAQ=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=LlFOQFr1Fb9TM68/OfSr9iuAWNucvdc9YWPtfu5mszVvjpQxbLfOXsDJpEW4BH0cd JbvpC0NGhdqsEmrBzCKi1WvpO+GgMmhkRPB/2jBq100Ec+i+ZVdkqjl2FjM7Q63hXL uMdgvuSVZmtbscppcd6XWOA9jnFuf4CBwRZLjUbc= To: Mike Schinkel , Rowan Tommins , Robert Hickman Cc: PHP internals References: <3ca6d665-1a4f-8f7a-c82a-2e899f2e8df1@gmail.com> <44ba543d-b6eb-888b-9ed5-0f1e9d3b53b9@gmail.com> <8E382251-AE41-4BD9-A5F8-135D11B9E10D@newclarity.net> Autocrypt: addr=d.h.j.takken@freedom.nl; keydata= xjMEXimHTRYJKwYBBAHaRw8BAQdAzvRUI24yOGvteVk9N6VKIt425fNgg0P1rvD2WQLGP+fN JERpayBUYWtrZW4gPGQuaC5qLnRha2tlbkBmcmVlZG9tLm5sPsKtBBMWCAA+FiEEvtrj9qG2 TA2YmjvLhef0X6cSlpAFAl4ph00CGwMFCQlmAYAFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AA IQkQhef0X6cSlpAWIQS+2uP2obZMDZiaO8uF5/RfpxKWkPywAQChh9Z1jSvitkT3sIipwMlk dnUlYY5Ue3lHBBhF6pQUOwD/XtEz/fsjvqE/GpjJhXpxNodwKjLhaUiFe9qRwwH/5QXOOARe KYdNEgorBgEEAZdVAQUBAQdAMNSCUI0PnOjjrFKZDAFRQzKLVDCINuFNgsXh0snmlUwDAQgH wpUEGBYIACYWIQS+2uP2obZMDZiaO8uF5/RfpxKWkAUCXimHTQIbDAUJCWYBgAAhCRCF5/Rf pxKWkBYhBL7a4/ahtkwNmJo7y4Xn9F+nEpaQEYUA/2mZ3uEN0JTRUZbxHGBMB4IhQw0cdIML FpFrTycqUCXCAQD5rWXomBWVD/DRHk7O3KjNsek9F1DEZgGeZ5pPmNF/Dg== Message-ID: <59f7df20-d89e-4076-d329-3a456bfb139a@freedom.nl> Date: Sat, 25 Jan 2020 23:35:28 +0100 MIME-Version: 1.0 In-Reply-To: <8E382251-AE41-4BD9-A5F8-135D11B9E10D@newclarity.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US X-Virus-Scanned: clamav-milter 0.102.1 at c03mi01 X-Virus-Status: Clean Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Add viable long running execution model to php 8 From: d.h.j.takken@freedom.nl (Dik Takken) On 25-01-2020 23:03, Mike Schinkel wrote: > Then we could look to prior art with GoLang channels where they "Communicate to share memory" and do not "Share memory to communicate." IOW, add an API that allows a regular PHP page to communicate with a long-running page. This would decouple and allow for better testing, and hopefully fewer hard to track down bugs. Go channels are about solving problems related to true concurrency: Multiple threads concurrently handling requests in a single shared memory environment. I think Robert is talking about sequential request handling in a single shared memory environment. Regards, Dik Takken