Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:24234
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <001301c69cac$39025540$07000100@OHRLVN4523SG>
To: "\"Andrew MatherBt\"" <an.dromeda@btconnect.com>
Cc: <internals@lists.php.net>
References: <200606302354.02272.an.dromeda@btconnect.com>
Date: Fri, 30 Jun 2006 18:18:02 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
Subject: Re: TSRMLS_D/C persistence
From: pollita@php.net ("Sara Golemon")

> How long are the TSRMLS_D/C parameters good for?
>
The life of a given thread.

> Can the resultant tsrm_ls value be safely stored?
>
Yes, but only during the life of a thread.  For practical purposes, you 
should consider this to mean the life of a request since there is no 
guarantee that subsequent requests will be serviced by the same thread.

> I presume the answer is no, and these paramters
> should be passed in each time a function is called,
> but I would be curious to know differently, if for example
> it could be passed in once at (external object) creation time,
> and that object could use the trsm_ls directly, rather than the
> TSRMLS_D/C semantics.
>
Yes, and I've done that on more than one occasion.

A given tsrm_ls value is tied to a thread (and uniquely identifies that 
thread).  Since a given request never jumps from one thread to another (It 
stays in the thread it was born in), the tsrm_ls you get at one point in a 
request will be the tsrm_ls you get at another point in a request.

-Sara
http://blog.libssh2.org/index.php?/archives/22-What-the-heck-is-TSRMLS_CC-anyway.html