2012/3/7 Torsten Förtsch :
> Yes, in mp1 it did. Not so in mp2.
Oh, I see this was covered on the dev list. It doesn't call
perl_destruct() because it may be running under threads, which mp1
didn't need to worry about.
- Perrin
On Wednesday, 07 March 2012 08:06:37 Perrin Harkins wrote:
> It doesn't call perl_destruct()? I thought it did in mod_perl 1
Yes, in mp1 it did. Not so in mp2.
static apr_status_t child_terminate(void *data) {
apr_pool_t *pool = (apr_pool_t *)data;
/* On the first pass, re-register so w
[Sorry, that last message was sent by accident. I set my phone to
require confirmation so it won't happen again.]
2012/3/7 Torsten Förtsch :
> 2) the way child_terminate() exits is quite nasty because it simply calls
> exit() at C level. That means neither END blocks nor PerlChildExitHandlers are
- Perrin
On Mar 7, 2012 7:00 AM, "Torsten Förtsch" wrote:
> On Friday, 02 March 2012 13:49:34 Perrin Harkins wrote:
> > You can use $r-->child_terminate().
>
> 2 remarks:
>
> 1) you can use this method at any point in the request cycle. It marks the
> process to be terminated when the current req
On Friday, 02 March 2012 13:49:34 Perrin Harkins wrote:
> You can use $r-->child_terminate().
2 remarks:
1) you can use this method at any point in the request cycle. It marks the
process to be terminated when the current request is done.
2) the way child_terminate() exits is quite nasty becaus
> Bouncing means restart the application to bring the current changes and new
> data to the cache. We can't use the following logic as there are huge
> number of existing data cache and perl modules involved. So the changes
> will be massive.
Keeping code in RAM is fine (that's one of the
On 2 Mar 2012, at 19:04, Shibi Ns wrote:
>
> Bouncing means restart the application to bring the current changes and new
> data to the cache. We can't use the following logic as there are huge number
> of existing data cache and perl modules involved. So the changes will be
> massive.
>
> S
Bouncing means restart the application to bring the current changes and new
data to the cache. We can't use the following logic as there are huge
number of existing data cache and perl modules involved. So the changes
will be massive.
Shibi
On Fri, Mar 2, 2012 at 4:51 PM, André Warnier wrote:
On Fri, Mar 2, 2012 at 3:20 AM, Shibi Ns wrote:
> I would like terminate current sever Child process after the end of current
> request because some data is cached and data is changed after the process
> creation. The data cached during InitChild phase
>
> Is it possible ?
It certainly is! You
Le vendredi 02 mars 2012 à 15:53 +0530, Shibi Ns a écrit :
> Not each request , it's based some data change in database and this
I can't help directly, but your post reminded me of this quote :
There are only two hard things in Computer Science: cache
invalidation and naming things.
--
On Fri, Mar 2, 2012 at 3:32 PM, André Warnier wrote:
Shibi Ns wrote:
I would like terminate current sever Child process after the end of
current request because some data is cached and data is changed after the
process creation. The data cached during InitChild phase
Is it possible ?
It
Not each request , it's based some data change in database and this could
happen couple of times in day that's all. We really don't want to go ahead
bounce the application in order refresh the cache
On Fri, Mar 2, 2012 at 3:32 PM, André Warnier wrote:
> Shibi Ns wrote:
>
>> I would like terminat
Shibi Ns wrote:
I would like terminate current sever Child process after the end of
current request because some data is cached and data is changed after the
process creation. The data cached during InitChild phase
Is it possible ?
It is certainly possible (*), but really, really, really inef
I would like terminate current sever Child process after the end of
current request because some data is cached and data is changed after the
process creation. The data cached during InitChild phase
Is it possible ?
Which phase should i do this
--
--Shibi Ns--
14 matches
Mail list logo
