Resending message because:
A) I forgot to send to the list
B) there's another option that may be easier.
I just tested this so I know it works.
1) Create the file dhandler in your document
root for mysite.com.
2) Add this code:
<%init>
my $arg = $m->dhandler_arg;
$m->redirect("http://mysite2.c
correction.
http://myserver.com/spanish/* gets rewritten to http://myserver2.com/*
Diona Kidd wrote:
I hope that someone will take the time to read this and help. I'm a
bit stumped. If I've posted this to the incorrect list, please advise.
This seems to be some combo of mod_perl, apache and
I hope that someone will take the time to read this and help. I'm a bit
stumped. If I've posted this to the incorrect list, please advise. This
seems to be some combo of mod_perl, apache and Mason.
I have two apache instances running with Mason and mod_perl. I'm
rewriting
Hi list, i've prepared a first skecth of a Visual mod_perl guide, the main idea
is to facilitate mod_perl learning and adoption using a visual notation.
It's in native inkscape svg format in:
http://hans.opensource.cl/Visual%20mod_perl%20Guide.svg (347 Kb)
There is a png version in:
http://hans.o
a) threaded-perl which is significatly slower in most operation you are
executing
I've just heard they are "comparable" in speed.. how big can this difference
be?
In our application that heavily uses hashes and closures we
experience a 2x slow down, and seldom segmentation fault.
We fell
On Wed, 2005-12-07 at 14:42 -0200, Fredrik Lindmark wrote:
> I could actually make the tree in filestructure and let the leafs be
> isolated files i guess.
That's what I was going to recommend, but as Cache::FastMmap entries.
It will perform very well.
> but its still far from the perl local mem
On Wed, 2005-12-07 at 13:46 -0200, Fredrik Lindmark wrote:
> Optimal would be to share the memory locally inside mod_perl and run
> one process and many threads.
> i should have basicly the same speed as a process prefork, and
> non-repeating data in the cache memory.
You will lose performance d
On Dec 7, 2005, at 2:03 PM, Frank Wiles wrote:
memcache and other daemons could help out here but they take too much
time compared to perls internal data memory to access and write.
Since they are not really fit for complex hash trees without doing a
heck of data coping forward and back.. i woul
On Wed, 7 Dec 2005 13:46:04 -0200
Fredrik Lindmark <[EMAIL PROTECTED]> wrote:
> memcache and other daemons could help out here but they take too much
> time compared to perls internal data memory to access and write.
> Since they are not really fit for complex hash trees without doing a
> heck o
On Dec 7, 2005, at 10:09 AM, Tom Schindl wrote:
Was running prefork apache 2.0.52 earlier. without any of these
symptoms..
Im switching to the worker in an attempt to improve the performance,
I don't think that you gain much performance at least on the mod-perl
side of the story because a you
Fredrik Lindmark wrote:
> On Dec 6, 2005, at 7:00 PM, Frank Wiles wrote:
>
>>> And im not starting up new threads myself.. i rely on apache on this
>>> so it feels like i should be in a safe enviroment here..
>>
>>
>> Have you tried the same code with the prefork MPM? While I know
>> there ar
11 matches
Mail list logo
