Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108292
MIME-Version: 1.0
References: <CAMuFt-6V24w6o8-hoPeRETCtfW25OtQ3KwdYprpYoQqpNQ2OsQ@mail.gmail.com>
 <3ca6d665-1a4f-8f7a-c82a-2e899f2e8df1@gmail.com> <CAMuFt-6Urf=7rXgR08_OsNSkBQeKVR84DisCc+2kyQXcJPuq0g@mail.gmail.com>
 <44ba543d-b6eb-888b-9ed5-0f1e9d3b53b9@gmail.com> <8E382251-AE41-4BD9-A5F8-135D11B9E10D@newclarity.net>
 <c2848f32-b06f-6711-8cbd-7fcba263ce29@gmail.com> <fd2455d3-ce1b-c699-a372-cab2eef0f280@cubiclesoft.com>
In-Reply-To: <fd2455d3-ce1b-c699-a372-cab2eef0f280@cubiclesoft.com>
Date: Tue, 28 Jan 2020 15:59:08 +0000
Message-ID: <CAJvSBVN0ybvXsrRnw5nUdAUAeRZ9vEom=pkJ7JCsqP8qfSfx9A@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000ffa807059d354f53"
Subject: Re: [PHP-DEV] Add viable long running execution model to php 8
From: phpmailinglists@gmail.com (Peter Bowyer)

--000000000000ffa807059d354f53
Content-Type: text/plain; charset="UTF-8"

On Tue, 28 Jan 2020 at 14:26, Thomas Hruska <thruska@cubiclesoft.com> wrote:

> People tend to write WebSocket servers in NodeJS partly because they
> don't realize that PHP can already do the same.  Example:
>
> https://github.com/cubiclesoft/php-drc


I didn't realize, so this is a great share. Thanks.


> WebSocket generally introduces network and processing overhead - HTTP
> headers and parsing for setup + framing protocol handling.  In many
> cases, a simpler "JSON blob per newline" approach works just as well (if
> not better) and can afford better isolation and performance models (i.e.
> not everything has to be WebSocket).  There are plenty of flaws inherent
> to the design of the WebSocket protocol itself (some are
> security-oriented) and so anything built on it shares those flaws.
>

This critique of WebSockets sounds similar to that of https://mercure.rocks/,
which uses HTTP/2 and Server-Sent Events instead of WebSockets.

I'm interested in WebSockets because I've been following the development of
Phoenix LiveView [1] for the last 13 months. Something similar in PHP would
be awesome (though the statelessness of PHP will complicate matters), but
when I looked at Swoole et al they wouldn't work with my existing
framework-based code. An approach that avoids rewriting, like some form of
built-in support in the language would be good for this alone.

Peter

1.
https://dockyard.com/blog/2018/12/12/phoenix-liveview-interactive-real-time-apps-no-need-to-write-javascript

--000000000000ffa807059d354f53--