On Thu, 2005-02-10 at 17:48 -0200, Leo wrote:
> Because application data should be the same across all processes (and I
> didn't think to use your suggestioned solutions below) when a request
> comes in, I tie the application session, check to see if my modification
> counter are equal. If it
Thanks Perrin
Perrin Harkins wrote:
Yes, although I think you mean "proxy" rather than "redirect."
You're right. mod_proxy
However the configuration of my
lightweight apache seems daunting.
It's not very hard to set up reverse proxying. You don't even need
mod_rewrite for the basic thi
On Thu, 2005-02-10 at 16:56 -0200, Leo wrote:
> As a slight adaptation, I could have an apache server dedicated to each
> virdual domain waiting on some high port number. And configure a
> lightweight apache on port 80 (serving lightweight stuff for all domain)
> to redirect (using mod_rewrite
Hello all:
I have apache2 setup with virtual domains. I am thinking about hosting
some mod_perl pages in a number of domains.
I don't anticipate much traffic for now, so I can experiment with this
stuff :)
Issue 1:
What strategies can I use to separate or isolate memory per virtual
domain. I
> > should building a DSO in mod_perl 1.x versions just be avoided?
>
> I think so, and so I think does Randal. This was discussed briefly
> here not long ago in a couple of threads, check the archives.
But note, that in DSO version graceful restart works perfectly (the
clients does not notice a
