Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85592
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.169 as permitted sender)
Message-ID: <551ABCAF.4070008@gmail.com>
Date: Tue, 31 Mar 2015 16:26:39 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <CAH8MpnknSgzZEpsgqwfNMq5h8C5eM5RVREjvLwCA5YxLhMKc6Q@mail.gmail.com> <551AAB20.6060100@luni.fr> <CAH8MpnnxmD5+cd1jmndBTV7XA5TQTseXVE-p-D0tsqMh7=ZfDw@mail.gmail.com> <551AB705.5040001@hristov.com>
In-Reply-To: <551AB705.5040001@hristov.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: HTTP/2 and Websocket support in 7.x versions
From: rowan.collins@gmail.com (Rowan Collins)

Andrey Hristov wrote on 31/03/2015 16:02:
> 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. 

Isn't the point that to get a real advantage from these technologies, 
the *userland* needs to be aware of threads / events? That's what 
requires a fundamental rethink of the language.

TSRM/TLS allows you to drop from one-process-per-request to 
one-thread-per-request, but it doesn't save you the expense of 
repeatedly building up and tearing down an execution environment.

Regards,
-- 
Rowan Collins
[IMSoP]