Re: "Linux Knowledge Base"

[Micah Yoder <LYoder@cyberis.net>]

"Dana M. Diederich" wrote:

> Not quite.  mod_perl keeps a persistent interpreter resident in memory,
> inside the web server.  (I'm not sure if it's a different process, or
> actually in the httpd space, but it's certainly persistent.)  Speed

I believe mod_perl keeps a perl interpreter inside EACH httpd process -
that's why it uses so much memory!

> savings come primarily because a new interpreter doesn't need to be loaded
> at every cgi invocation.  The perl interpreter is rather large.

And a lot of the speed savings occur because the Perl scripts do not
need to be recompiled each time.  The perl object code stays in memory,
ready to run.

> I guess my point is mod_perl is ok, but let's not let it slow down
> development for any reason.  If that happens, we can get to it later.

Well, I think we might as well start out with it.  The differences in
programming are very minimal, right?  I think we will want/need it
eventually, so this will save us from switching over.

> Using fonts can be problematic with older browsers.  (Third generation
> browsers.)

We don't even need to use fonts.  Regular text is fine with me, maybe
altering colors and sizes.

> Over-engineering web pages is a trap I've fallen into more often than I like
> to admit over the years.  Some of the BEST web sites I've seen out there
> have < 50k of graphics, and nothing more than HTML 1 technology.  I guess the
> key thing to remember is that it's content that makes the site, not the web
> pages.

Right!

> Here's a minimal perl script that connects to a DBI data sources and grabs
> some data:

Thanks, that looks like a useful example...