Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:15238
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
	s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
	b=rS0w2PGAxBzLUyX/HBurnaqsZ2ZfXgyaMJtVKbns8P5m6g1GUoUmNIyxP7wOjeEaRMBZgvi0aLliGh7dfGZ5zI6hPuMyKWyf2GOyzvlfWr8+IiFnd615a4oPKtYOWW9EwW7OneaVP8em8Q2Rv3Ug3J2fuaXr5kw+wru+3yiGlXs=
Message-ID: <4e89b426050228215637f000f9@mail.gmail.com>
Date: Tue, 1 Mar 2005 00:56:46 -0500
Reply-To: Wez Furlong <kingwez@gmail.com>
To: Bob Beaty <drbobbeaty@gmail.com>
Cc: Vadka <vvs_php@nsrd.sinp.msu.ru>, internals@lists.php.net
In-Reply-To: <729eaf208f6ab01379951b88d8f90b76@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <2005022807371112877%drbob@TheManFromSPUDcom>
	<42233717.9050107@akbkhome.com>
	<Pine.LNX.4.60.0502282204290.2142@nsrd.sinp.msu.ru>
	<729eaf208f6ab01379951b88d8f90b76@gmail.com>
Subject: Re: [PHP-DEV] How to embed PHP5 into multi-threaded C app?
From: kingwez@gmail.com (Wez Furlong)

ZTS enabled PHP has "strong thread affinity".
Calls into the engine are thread-safe provided that you have
previously initialized the engine on that thread.

Note that you should not efree() memory allocated on one thread from
outside of that thread, on pain of segfault.  eg: resources from one
thread cannot be safely passed on to another thread.

--Wez.



On Mon, 28 Feb 2005 14:24:05 -0600, Bob Beaty <drbobbeaty@gmail.com> wrote:
> Which is my concern.
> 
> I've looked at the code differences, and it appears that this
> modification works for running different source files through the
> engine, but I'm concerned about the safety of zend_eval_string() if I
> initialize the engine in one thread and then try to have several
> threads calling zend_eval_string() on different strings.
> 
> I'm not convinced that simply making the php_embed_module thread-local
> is going to work either. I'm concerned that the engine was written with
> the idea that only one thread can be initializing the php_embed_module
> and making calls to zend_eval_string(). If this is the case, then I'd
> have to re-write a lot more than php_embed.c to get thread-safety out
> of the engine.
> 
> Or am I on the wrong track?
> 
>                 Bob
> 
> 
> On Feb 28, 2005, at 1:08 PM, Vadka wrote:
> 
> >
> > On Mon, 28 Feb 2005, Alan Knowles wrote:
> >
> >> these still need tidying up alot, but the do work.
> >> http://docs.akbkhome.com/php_embed.c.txt
> >> http://docs.akbkhome.com/php_embed.h.txt
> >> replace the code in php_embed with them, make sure you compile with
> >> the zts enabled, and the macros's are similar to the original embed
> >> (use threaded start call at application start up, and thread start
> >> /start end within the pthread_start(...callback..) method
> > Thread safeness is not a problem for a single thread.
> > The problem is to call user functions from different threads
> > (tsrm_ls pointed to somewhere in different threads, global vars etc
> > are not protected).
>         Thanks,
>                 Bob (drbob@TheManFromSPUD.com)
>         The Man from S.P.U.D.
>         We will write no code before it's designed.
> 
>