Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
From: "Mladen Turk" <mturk@mappingsoft.com>
To: "'Tomcat Developers List'" <tomcat-dev@jakarta.apache.org>
Subject: RE: [PROPOSAL] RegisterNatives
Date: Sun, 9 Jun 2002 21:37:09 +0200
Organization: Mappingsoft
Message-ID: <000601c20fed$0f147560$5c00000a@GISDATA.ZG>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <80F5674514B4D311BAFC0040F6A45EEE2CA890@ntserver>
Importance: Normal


> -----Original Message-----
> From: Ignacio J. Ortega [mailto:nacho@siapi.es] 
> Sent: 9. lipanj 2002 20:20
> To: 'Tomcat Developers List'
> Subject: RE: [PROPOSAL] RegisterNatives
> 
> 
> > that out. The
> > apr_initialize for IIS should be called
> > IMO from DllMain  in jk_isapi_plugin, but I'm not familiar 
> with that.
> > 
> 
> I think DLLMain is not a very good place to put apr_initialize, in IIS
> the DLL never gets unloaded after the IIS process start.. and if we
> finally come with a way to restart the whole jk2, 
> apr_initialize should
> be called at Filter or Extension start, anyway there are 3 call to
> apr_initialize, there is anoher at jk_env.. i will get rid of that one
> too..

The apr_initialize is IMO intended to be the pool container for the
entire process life.
The concept of subpools is meant to be used for inproc restarting like
Apache do. There is no need to that with
apr_initialize/apr_terminate.
But if the Filter or Extension start is unique call to the dll then it's
matter of choice I think.

Consecutive calls to apr_initialize only increments the reference count,
and to call the 'true' apr_terminate that count must be 1.

MT. 


--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>