Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:121503 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 64656 invoked from network); 29 Oct 2023 03:30:48 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 29 Oct 2023 03:30:48 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id D4B4D180212 for ; Sat, 28 Oct 2023 20:30:47 -0700 (PDT) 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,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE 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-pg1-f175.google.com (mail-pg1-f175.google.com [209.85.215.175]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Sat, 28 Oct 2023 20:30:47 -0700 (PDT) Received: by mail-pg1-f175.google.com with SMTP id 41be03b00d2f7-5a9bf4fbd3fso2727261a12.1 for ; Sat, 28 Oct 2023 20:30:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1698550246; x=1699155046; 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=s5KYAZuvtn1+ftKwTwmlkTtvVfjqB76i/NIXupyisgo=; b=Lr7gbEAcZzk5jseWqCpOLOGJRNxitplGDL0Ldcg/Nl3QDEqWtG175sKZe9aHk4wNsT P4A0x2e7pRA7SL9j3cb9JMCQ8U45zA6nP6ng4HX81NEDxaKry6VHgEyHaUgLzw0yHNd8 /4jRRhs1bv+q+cU+sHvoVpU8I4qQlM23P7EqiaRAUSSUH1Ra7xenOZmY+As7YW8AOb5m f7X+JJuYUoqU90xgslVft8ZNWfvmkOXEx7Q5fZ5jmWhVXZb+xtw2WngKu7eTvhZ8nGA5 GZxqJ7uJ4Lk6aoOzT5fyWbq9KszIMOSKw3+465e1lJd8/AbJtznOixPvMT3QbzMXJMQX ++ZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698550246; x=1699155046; 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=s5KYAZuvtn1+ftKwTwmlkTtvVfjqB76i/NIXupyisgo=; b=pvjS/0uz07KMvPZG+Qpk3wAYTgZjBmaRHXKq/tmWS00ik93rO8+jUmy+8rgV/sm4B3 dyYAgyxmvLDu+Mnf6ou9EiQqFau0xureIFW3NdhcQCgjh5AF+u0MbejOLh1GoGUf3Zsz G36+/rYuk/IQ5BmIrGxFt1tHQ3xC4UdRMBIp0/i+LHV5gmkq1SKq4JTxqlQ1yCnuLitj GZVWRooPArSrFc9ESl4ijUoijNFmPT1gURMQzPPAC4WQepYZoeROxZWMyJH/fhZRTZsm c2Z70JSrcuHx8PDtIGWqd5O4Q418z6+EDhfoBF0mSNLuYsLVF3dt4xoZFR6NCmopYSgI CTjg== X-Gm-Message-State: AOJu0YxCDoogYum/QNJFvwHAHRLYpQk3wt6VuDOAHc6Ue3f9uEyHjjij SFwuYHwZ+JTKueDEpkqsRJmEC83x63dQimm+gZg= X-Google-Smtp-Source: AGHT+IGIdFHNRaI1/AGAYF8BLIvWR1rQ3XZ7axuykJY3DsjUfurlsBfMZeuYIJbCFcFwehxhq+XlbxQp6bM6UM7VQZQ= X-Received: by 2002:a05:6a20:3942:b0:14d:2b8d:d62f with SMTP id r2-20020a056a20394200b0014d2b8dd62fmr9257188pzg.47.1698550246306; Sat, 28 Oct 2023 20:30:46 -0700 (PDT) MIME-Version: 1.0 References: <1698415135.52648521@f511.i.mail.ru> In-Reply-To: Date: Sat, 28 Oct 2023 20:30:32 -0700 Message-ID: To: juan carlos morales Cc: Kirill Nesmeyanov , internals Content-Type: multipart/alternative; boundary="00000000000010778e0608d28cc4" Subject: Re: [PHP-DEV] Discussion - PHP with distributed programming features. From: jordan.ledoux@gmail.com (Jordan LeDoux) --00000000000010778e0608d28cc4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Oct 28, 2023 at 4:35=E2=80=AFPM juan carlos morales < dev.juan.morales@gmail.com> wrote: > > > El El s=C3=A1b, 28 de oct. de 2023 a la(s) 19:25, Jordan LeDoux < > jordan.ledoux@gmail.com> escribi=C3=B3: > >> >> >> On Sat, Oct 28, 2023 at 10:54=E2=80=AFAM juan carlos morales < >> dev.juan.morales@gmail.com> wrote: >> >>> >>> >>> What I mean is more about =E2=80=A6 migrating a running php instance to= another >>> node or another php instance, in fact your php code is running, suddenl= y >>> we >>> Need to move to another node, how to do it? >>> >> >> This seems less like a discussion about a PHP feature and more like you >> asking internals for tech support at work, honestly. As far as I know, >> there isn't a way to do what you're asking, because you can accomplish t= he >> same thing much easier by designing your application better to make API >> calls to services, which is what people have already suggested. The PHP = way >> to handle the root cause of your problem (too many resources being used = on >> a single machine) is to divide the application into services and use API= s, >> often through sockets, the delegate work to those services. >> >> There are also other ways of handling this common problem in web >> application architecture. You can break up the request into multiple >> requests on the client side so that the user sees progress happen in >> chunks. You can use tools like RabbitMQ or other queuing services to >> perform certain long-running tasks asynchronously. You can use more >> powerful hardware or provision more capable nodes. >> >> In fact, several of these actually fall under the Actor/Object or >> Dataflow model of implementing Distributed Programming. What PHP does no= t >> support is the Distributed Shared Memory model of implementing Distribut= ed >> Programming (which is what you are asking about apparently) because doin= g >> so would almost certainly make PHP worse at the things it is well suited >> for, would massively complicate the work of maintaining and developing t= he >> language for the contributors to the language, and would be a massive >> undertaking to implement in the first place. >> >> PHP has distributed programming features. In fact, all of the suggestion= s >> you have received so far ARE ways of doing distributed programming >> features. But internals is not your, or my, or anyone else's personal te= ch >> support channel, and personally it feels like you haven't explained what= it >> is you want to discuss with internals about improving or changing PHP's >> support for distributed programming. Are you interested in working on an >> RFC to clone a PHP process onto a remote box? I can't imagine that would >> get much support here, or be something that is very simple to do. >> >> Jordan >> > >> > Hello Jordan, thanks for the reply. When I read you, I have the feeling > that you are a little angry about my question, please dont. > > It is a very honest question, that do belong to the internals, because if > PHP does not have a way to do it, I would like to think a way to do it > (despite the fact someone believes is useful or not, it is just me). > > So again, thanks!, dont get mad :D, and I will come back later on this > topic, in a more clear way, maybe I am not expressing myself clearly. > > Regards > I'm not angry at all, I just wanted to focus in on a discussion that is relevant to the internals mailing list. Most of the ideas here, including the ones I've proposed, come from our own experiences and there's nothing wrong with that. But I didn't see anything that looked like a discussion and I wanted to be clear about what I think this list is for, and what kind of discussions might be productive. I don't think that what you are talking about would be very useful, because I expect that it would be complicated for very little benefit. But if you think this is a way to improve the language, then I would listen. I just wasn't hearing that. It is also possible I am not understanding very well. Jordan --00000000000010778e0608d28cc4--