[prev in list] [next in list] [prev in thread] [next in thread] 

List:       apache-modperl
Subject:    configuration question
From:       Jonathan <jvanasco () 2xlp ! com>
Date:       2006-04-24 1:57:33
Message-ID: 5DA9CE78-EBBC-4B08-B8C0-25AFD093068A () 2xlp ! com
[Download RAW message or body]

I've got a question on a setup

right now, i have modperl set up as such:

<virtualhost>
	PerlRequire /path/to/startup.pl
	PerlSetEnv PERL_RLIMIT_DEFAULTS On
	PerlModule Apache2::Resource
	<location /api/ >
		SetHandler 'modperl'
		PerlResponseHandler 'myapp::api'
	</location>
</virtualhost>


of course there are a bunch of location blocks - /api/ , /account/ etc

I need to move api (and a few other items) from /api/ to  
api.mydomain.com

naturally, that means a new virtualhost container

my question is this - api and a the other items still share 95% of  
the code base, including the configuration variables that are loaded  
in startup.pl

what's an efficient way of keeping everything maxxed on shared memory?

my first thought was to do (xmlish to save typing)

====
PerlRequire /path/to/startup.pl
<virtualhost/>
<virtualhost/>
<virtualhost/>
====

except that would be too easy.  see mp isn't serving these items  
directly - this is a multi-server setup.  so *most* requests are  
coming from 127.0.0.1, but others will hit the real domain.

can anyone offer a tip?  i'm thinking that the only thing to do is to  
bind each handler to a different port and a different vhost.





[prev in list] [next in list] [prev in thread] [next in thread]