On 7-Aug-06, at 12:48 PM, David Nolan wrote:
Matt,
Reading the comments on your blog post I see that you still intend
to make it possible to use AxKit2 behind an apache frontend. Will
that use mod_perl, or something else?
Apache and mod_perl are critical to the applications we develop,
because we rely on apache to provide SSL and user authentication
via pubcookie (single sign on system for web), and we rely on
mod_perl to cache database connections and avoid compiling 80K
lines of perl on every web request. (Yes, 80K is a real number from
our primary web app (including whitespace.), but that system isn't
using AxKit now... if we ever reimplement it using our AxKit based
web toolkit I expect the size of the perl component would go down
dramatically.)
I could see the mod_perl functionality being replaced in AxKit2,
but I don't think the apache features we rely on could be replaced
easily.
Yes you can still frontend it with Apache, in the same way you do now
with mod_perl apps in the "front end reverse-proxy" setup.
My basic view on this is that you should be able to let the frontend
do SSL (and pubcookie whatever that is) and still proxy cleanly to
the backend.
DBI caching becomes trivial as there's only one process. Though we'll
have to come up with a decent way to do long running processes.
Probably involves forking off the same way plugins/serve_cgi does.
Matt.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
