estion was getting the perl core out of the address space of
the httpd process entirely :)
Velocigen does this nicely (though there is a performance penalty) and even
allows degicated machines runnign the perl services that talk to the
webserver over sockets.
Ken
---
Soulhuntre
(icq# 275066)
ht
ight? The Apache::Registry module allows us to speed up "cgi" processes,
but not page scripting per se?
Ken
---
Soulhuntre
(icq# 275066)
http://www.soulhuntre.com - my world
http://www.dotpublishing.com - my income
http://www.virtualchemy.com - my company
http://www.the-estate.com - my passion
figurable number) of perl's running that round robin to work
with Apache::ASP to render pages?
This should also seperate out the systems a bit for stability.
Ken
---
Soulhuntre
(icq# 275066)
http://www.soulhuntre.com - my world
http://www.dotpublishing.com - my income
http://www.virtualch
encouragement
or last minute red flags will be appreciated, we finalize on Friday :)
Ken
---
Soulhuntre
(icq# 275066)
http://www.soulhuntre.com - my world
http://www.dotpublishing.com - my income
http://www.virtualchemy.com - my company
http://www.the-estate.com - my passion
site needs anyway.
Ok... that makes sense :)
On a side note... is mod_perl/apache on linux compatible with IIS/operlex
from activestate on the Win32 side?
If so, that's a big boost for me...
Ken
---
Soulhuntre
(icq# 275066)
http://www.soulhuntre.com - my world
http://www.dotpublishing.co
can use modperl/apache/::ASP under linux, but the same setup
> does
> | not seem stable under win32 - and the activestate ASP perlex stuff does
> not
> | seem completely compatible.
>
> Can you give me more detail on the incompatibilities?
Well, let me turn tha
Hiya!
Ok, we are getting ready to head out on a rather largish project, and it is
time to settle on a set of tools.
The primary issues:
1) Quick development
2) Ability to migrate easily to/from win2000 servers (Apache/win32 is fine)
3) Minimum arcane traps
4) Minimum destabilization of the s
