Re: [PECL-DEV] A question about Extension documentation

2012-10-28 Thread Terry Ellison
On 28/10/12 19:37, Rasmus Lerdorf wrote: On 10/28/2012 11:29 AM, Terry Ellison wrote: I have a simple Q. /snip/ Can someone please point me to the documentation and installation for your Documentation system so that I can use it -- and the github links to documentation source for example extensi

Re: [PECL-DEV] A question about Extension documentation

2012-10-28 Thread Rasmus Lerdorf
On 10/28/2012 11:29 AM, Terry Ellison wrote: > I mentioned last month that I am developing an experimental lightweight > fork of APC intended primarily at shared hosting / CGI / FastGCI > stacks. I have a simple Q. > > I am used to developing with the full documentation set embedded in any > sour

[PECL-DEV] VCS Account Request: ecaron

2012-10-28 Thread Eric Caron
To help maintain and support the Solr extension (see pecl-dev email on http://marc.info/?l=pecl-dev&m=135066423910915&w=2 for more information.) -- PECL development discussion Mailing List (http://pecl.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php

[PECL-DEV] A question about Extension documentation

2012-10-28 Thread Terry Ellison
I mentioned last month that I am developing an experimental lightweight fork of APC intended primarily at shared hosting / CGI / FastGCI stacks. I have a simple Q. I am used to developing with the full documentation set embedded in any source that I develop. (Doxygen is my documentation tool

Re: [PECL-DEV] Interesting APC behaviour

2012-10-28 Thread Rasmus Lerdorf
On 10/28/2012 08:04 AM, Ángel González wrote: > El 28/10/12 14:52, Rasmus Lerdorf escribió: >> On 10/28/2012 04:54 AM, Terry Ellison wrote: >> >>> From the perspective of a production sysadmin, I've always just set >>> apc.stat=0 but then cleared the cache following any change. This gives >>> the

Re: [PECL-DEV] Interesting APC behaviour

2012-10-28 Thread Ángel González
El 28/10/12 14:52, Rasmus Lerdorf escribió: > On 10/28/2012 04:54 AM, Terry Ellison wrote: > >> From the perspective of a production sysadmin, I've always just set >> apc.stat=0 but then cleared the cache following any change. This gives >> the best of both worlds: the performance dividend of no

Re: [PECL-DEV] Interesting APC behaviour

2012-10-28 Thread Rasmus Lerdorf
On 10/28/2012 02:41 AM, Gopal Vijayaraghavan wrote: > If I'm not wrong, this only breaks APC when include_once_override is turned > on. > > My vote is to drop the apc.include_once_override and make APC a bit > simpler & neater. > > I've found that it behaves rather inconsistently when people sta

Re: [PECL-DEV] Interesting APC behaviour

2012-10-28 Thread Rasmus Lerdorf
On 10/28/2012 04:54 AM, Terry Ellison wrote: > From the perspective of a production sysadmin, I've always just set > apc.stat=0 but then cleared the cache following any change. This gives > the best of both worlds: the performance dividend of no stat'ing and > avoiding the weird gremlins that so

Re: [PECL-DEV] Interesting APC behaviour

2012-10-28 Thread Terry Ellison
On 28/10/12 06:32, Rasmus Lerdorf wrote: On 10/27/2012 03:50 PM, Stas Malyshev wrote: Hi! An APC-level fix might be to fix the include_once/require_once override implementation to go to the cache first to see if the inode is there and pull out the cached realpath and use that to check against

Re: [PECL-DEV] Interesting APC behaviour

2012-10-28 Thread Gopal Vijayaraghavan
If I'm not wrong, this only breaks APC when include_once_override is turned on. My vote is to drop the apc.include_once_override and make APC a bit simpler & neater. I've found that it behaves rather inconsistently when people start returning values from scripts. wrote: > On 10/27/2012 03:50 PM