Req #80643 [Opn->Sus]: Deliver an optimized WebSocket-Server implementation for the 80% of use-cases

Edit report at https://bugs.php.net/bug.php?id=80643&edit=1 ID: 80643 Updated by: requinix@php.net Reported by: ernesto dot sun at gmail dot com Summary: Deliver an optimized WebSocket-Server implementation for the 80% of use-cases -Status: Open +Status: Suspended Type: Feature/Change Request Package: Sockets related PHP Version: Irrelevant Block user comment: N Private report: N New Comment: This is too large of a request for a simple bug tracker. Please check out the internals mailing list. https://www.php.net/mailing-lists.php Previous Comments: ------------------------------------------------------------------------ [2021-01-18 20:11:32] ernesto dot sun at gmail dot com Description: ------------ Hello highly respected PHP-team. Thank you so much for the great improvements to version 7 and now, even 8 is out, that I don't know yet. Having done research again, how to realize a safe simple mini-websocket-server, I have noticed that you did not care all too much about this topic recently. So, please consider this: Provide a core-functionality (so that shared hosting will always have it) with the handful of typical operations people need to realize a simple in/out/-websocket-server with PHP. By focusing on the 80%-mainstream-usecases you might beat Node.JS both in speed and simplicity. You can focus on the essentials optimized as direct as possible with C and wow - that makes the next 30 years of global success to PHP ;) Tow more arguments: * The complete already existing socket-implementation is not affected and allows for the 20% special cases. * Instead of leading your users somehow to the 'UNIX Socket FAQ' (thats great ok), you can provide high-level examples of a safe and fast Chat-servers. Whats more convincing?! Thank you so much! All (=) Love, Ernesto ~:) ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=80643&edit=1