Hi Dan,
We have no commercial purpose on the swoole open source project. This is a purely technical project. If possible, we can remove the name of swoole, contribute the source code of swoole-src to php-src, and transfer the copyright. Here is just a technical discussion. My opinion is that if PHP will support fiber/green-threads, this is a major change, should redesign language syntax, standard library, ZendVM. This proposal must be discussed extensively and in-depth, should not make a hasty decision. There are 7 parts to consider with my experience: EventLoop API Fiber/Coroutine/GreenThread IO-Scheduler (Socket/FileSystem/ChildProcess/Signal/Timer/Stdout/Stdin) CPU-Scheduler Compatible with existing extesions (php_streams/ext-sockets/ext-redis/ext-mysqli/ext-pdo-mysql/ext-curl ...) and builtin-functions (sleep/gethostbyname/proc_open/file_get_contents) Service container, How to support php-fpm and provide a coroutine version of http server Coroutine communication, How to pass messages between two coroutines It’s nice to see php has such topic. This may be the key technology in the next generation of PHP. Thanks Tianfeng.Han ------------------ Original ------------------ From: "Dan Ackroyd"<dan...@basereality.com>; Date: Fri, Mar 12, 2021 05:50 AM To: "twosee"<tw...@qq.com>; "韩天峰"<ra...@swoole.com>; Cc: "Aaron Piotrowski"<aa...@trowski.com>; "php internals"<internals@lists.php.net>; Subject: Re: [PHP-DEV] [VOTE] Fibers Hi Twosee, Tianfeng.Han I was drafting a longer reply to you both, but I realised I might be missing some information. Please could you disclose the commercial interests of the Swoole maintainers, and the ties to the for profit companies that provide services implementing Swoole? Having people vote on RFCs who have ties to companies that provide services via commercial entities isn't unprecedented. For example zend.com has had employees who are involved in voting on RFCs, but to a large extent that was done openly, with all of them using zend.com email addresses. twosee wrote: > Of course, the Swoole community still expects to merge it into php-src at an appropriate time. What's your idea of an appropriate time and how do you plan to start this conversation? If something hasn't been merged back after 8 years, it sounds reasonably unlikely that it's ever going to be merged back. cheers Dan Ack
