Re: Refactoring our IO multiplexing layer
| From: | Levi Morrison | Date: | Tue, 17 Jun 2014 14:28:52 +0000 |
| Subject: | Re: Refactoring our IO multiplexing layer | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-74951@lists.php.net to get a copy of this message | ||
On Tue, Jun 17, 2014 at 4:04 AM, Julien Pauli <jpauli@php.net> wrote:
> So basically, the first question will be do we need it ?
I would like it, yes. Having a IO abstraction layer internally would
be really nice. I'm not up-to-date on all the PHP extensions that
would facilitate this behavior, but perhaps some improved version of
the libuv extensions would be great. I am not sure on the health of
those extensions (I believe there are at least two of them) but it's
worth investigating at least. Potentially it could save us some work
as well as well as give us a bit more confidence.
> Second question will be : do we use, and then link against libevent
> (or any other lib that could fit the need) , or do we develop our own
> layer, based on the FPM layer which is pretty nicely done (just not
> shareable elsewhere at the moment).
I also favor libuv over libevent; to be completely fair I have only
used both of them a little bit but I liked libuv a bit more.
We definitely shouldn't roll our own. If we had corporate funding then
rolling our own would have the advantage of not having to wait for
upstream merges for bug fixes, but I don't think we have the manpower
or interest to build and maintain our own.