Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79035
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain meituan.com designates 211.151.229.38 as permitted sender)
Content-Type: multipart/alternative; boundary="Apple-Mail=_5F4CD3DC-ED76-419B-BA0E-0CAF5631C356"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
In-Reply-To: <1416479430.15061.15.camel@kuechenschabe>
Date: Thu, 20 Nov 2014 19:19:17 +0800
Cc: Tigran Bayburtsyan <tigran.bayburtsyan@gmail.com>,
 internals@lists.php.net
Message-ID: <DA850E41-4C9C-49F8-8D30-D2048BD2EE1F@meituan.com>
References: <CAPU44xz2C-xRfTm+nUhD0nF9PTPgMyvJYtDRTOS_+4hADMGiug@mail.gmail.com> <1416479430.15061.15.camel@kuechenschabe>
To: =?GB2312?Q?Johannes_Schl=A8=B9ter?= <johannes@schlueters.de>
Subject: Re: [PHP-DEV] PHP SAPI module help
From: lanxiaolu@meituan.com (=?GB2312?B?wLwg0KTCsw==?=)

--Apple-Mail=_5F4CD3DC-ED76-419B-BA0E-0CAF5631C356
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=GB2312

How about writing this logic in an extension?  Because u can write your =
own RSHUTDOWN function to protect your data.

sorry for my poor english.

--
lanxiaolu

=D4=DA 2014=C4=EA11=D4=C220=C8=D5=A3=AC=CF=C2=CE=E76:30=A3=ACJohannes =
Schl=A8=B9ter <johannes@schlueters.de> =D0=B4=B5=C0=A3=BA

> Hi,
>=20
> On Tue, 2014-11-18 at 18:08 +0400, Tigran Bayburtsyan wrote:
>> I need to execute PHP code in some thread of my application and =
continue
>> excecution in another. Is is possible to somehow get all global PHP =
core
>> hashtables from first thread and restore PHP from that point in =
another
>> thread using that hashtables with all generated variables and =
functions ?
>=20
> PHP works request base. Meaning the idea is to have isolated
> shared-nothing requests.
>=20
> PHP can run in two modes:
>=20
>     1. In a global environment, or
>     2. in a threaded environment
>=20
> this is controlled by enabling or disabling ZTS - zend thread safety /
> TSRM thread-safe resource manager. In the first case you have a global
> state running one "request" at a time, theoretically this single =
request
> context can be accessd by multiple threads while access has to be
> guarded by some mutex.
> In the second case you can have multiple requests which separate =
state.
> Each of those is bound to a (posix|windows) thread sharing a context =
in
> this mode between different threads can't be easily done and requires
> patching (in non-public code I once created worker threads owning the
> PHP request and different threads can signal there to bypass, but =
that's
> a mess).
>=20
> The probably most simple SAPI using different threads is my pconn =
SAPI:
> https://github.com/johannes/pconn-sapi
>=20
> Except for source we don't really have good documentation on all the
> details. So please try to go through different SAPIs and try to
> understand them. Specific questions are welcome on this list.
>=20
> johannes
>=20
>=20
>=20
> --=20
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>=20


--Apple-Mail=_5F4CD3DC-ED76-419B-BA0E-0CAF5631C356--