You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Andrew Wilson <an...@aaaaaaaa.demon.co.uk> on 1996/04/27 14:49:37 UTC
Forwarded: Apache Suggestion (fwd)
This from Dave Hankins who brought us the mod_dld_elf module (as
yet unclaimed) a few months ago. He's describing a mechanism which
(loads/links) invokes custom code sitting in a module which is
designed to perform a specific task. Ok, so this looks like another
contender for 'ways to do stuff faster than ordinary cgi can do
it'.
Comments, if any, to Dave, not me.
Ay.
Forwarded message:
> Date: Fri Apr 26 16:56:08 1996 EDT
> From: Andrew.Wilson@cs.cf.ac.uk (Networker@JHM)
> To: Andrew.Wilson@cs.cf.ac.uk
> Subject: Forwarded: Apache Suggestion
> X-Mail-Agent: JHM (jhm.ccs.neu.edu 1709)
> Original-Date: Fri Apr 26 16:56:08 1996 EDT
> Original-From: Exedore (#2266)
> Original-To: Networker (#266)
> Reply-To: dhankins@hcf.aloha.net (Exedore@JHM)
> Resent-Date: Fri, 26 Apr 1996 21:57:48 +0100
> Resent-To: andrew@aaaaaaaa.demon.co.uk
>
> Along the lines of the new Script command in Apache 1.1...you're probably
> familiar, it lets you define an action for a kind of file that Apache doesn't
> natively support...raw HTTP handling of a specific type.
>
> Suggestion is a loadable module version of the same. Leaps and bounds more
> efficient than the scripted version (no execution nor parsing overhead). The
> server could link, use, and unlink the application, in the multi-threaded
> version, the linking and unlinking code would be responsible for loading and
> unloading as needed...The linux version of DL, for example, will link in what
> you request, and not *actually unlink* what you're done with until it's idle
> or until it needs that area of memory.
>
> It's a tad bit more intelligent than caching just the script to RAM (file
> cache) and continually doing the same execution/parsing overhead over it every
> time that type of file is accessed.
>
> Just a thought.
>