in reply to Re^2: A Perl Daemon
in thread A Perl Daemon

And yes getting rid of Apache is my goal here. I would like a Perl daemon. Something that loafs around with precompiled modules sitting in it just waiting to be used by a script that needs them. A kind of module pre-compiler.
I must say that I have at best and extremely limited experience in this application area, but... I can't understand what your stated goals as in the quotation above could have to do with "getting rid of Apache". That is: once you have your hypothetical perld, do you want to use it to run a webserver written in Perl instead of Apache? If so, then there are some. But I doubt this is what you really want...

Replies are listed 'Best First'.
Re^4: A Perl Daemon
by habit_forming (Monk) on Sep 09, 2005 at 13:34 UTC
    What was meant by "getting rid of Apache" was in reference to merlyn's response.

    The fact of the matter is that I have many different processes, that are not Apache, that come up on their own and use BigModuleTree.pm to do their work. I really like mod_perl and the way it handles things except for it's forking behavior. So a "standalone" mod_perl was the metaphor I was using to describe this perld idea.

    I still plan on using Apache to run the CGI's I have to run (with or without perld). I still plan on using mod_perl where ever I can (when not forking a bunch) but when not in Apache I would like to have something that could speed-up execution like mod_perl does. And since mod_perl accomplishes a lot of it's speed by being persistent... I thought, well why not a sort-of Apache divorced generalized mod_perl? That is where the idea started.

    --habit
[reply]

In Section Meditations