Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85591
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.181 as permitted sender)
MIME-Version: 1.0
Date: Tue, 31 Mar 2015 15:22:25 +0000
Message-ID: <CAH8Mpn=P5txCt_fmX0VdNf_XpEDaQ_vKot4XVAeG41QPqQPX-A@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11346e3c799a680512972abb
Subject: Re: Re: HTTP/2 and Websocket support in 7.x versions
From: rdlowrey@php.net (Daniel Lowrey)

--001a11346e3c799a680512972abb
Content-Type: text/plain; charset=UTF-8

> this ain't exactly true. Currently in MT environment the task of data
> separation is pushed to the TSRM by using TLS. Now, if TSRM is
> reimplemented in a fashion that the data is not stored by using TLS but
> other mechanism and cooperative multitasking is not something that
> can't be done.
> The truth is that userland is isolated from the process data space so for
> it it won't make a difference. It's just that using threads for
separation is
> the easiest thing (after process per script). The good thing is that TSRM
> is an abstraction for its clients.

How could we make this work in the absence of TSRM, though? I'm operating
under the assumption that any solution would need to work the same way
outside the auspices of TSRM. With process forking you'd be talking about
pretty complex inter-process signaling to try and accomplish equivalent
multitasking. This doesn't seem at all feasible to me on first glance
(though I've been wrong plenty of times in the past).

--001a11346e3c799a680512972abb--