httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Hartill <r...@imdb.com>
Subject mod_actions.c
Date Sun, 15 Dec 1996 21:23:58 GMT

There's an incomplete sentence in the header blurb.


Index: mod_actions.c
===================================================================
RCS file: /export/home/cvs/apache/src/mod_actions.c,v
retrieving revision 1.1
diff -c -r1.1 mod_actions.c
*** mod_actions.c       1996/12/10 05:02:52     1.1
--- mod_actions.c       1996/12/15 20:04:02
***************
*** 60,68 ****
   *
   * Action mime/type /cgi-bin/script
   * 
!  * will activate /cgi-bin/script when a file of content type mime/type. It
!  * sends the URL and file path of the requested document using the standard
!  * CGI PATH_INFO and PATH_TRANSLATED environment variables.
   *
   */
  
--- 60,68 ----
   *
   * Action mime/type /cgi-bin/script
   * 
!  * will activate /cgi-bin/script when a file of content type mime/type is
!  * requested. It sends the URL and file path of the requested document using
!  *  the standard CGI PATH_INFO and PATH_TRANSLATED environment variables.
   *
   */
  



-=-=-=--=-=-=-=-

Is there a way to stack handlers ?   e.g.

AddHandler server-parsed .html
AddHandler something-else .html

to say parse the SSI and then feed the results to the "something-else"
handler for more attention. Kinda like streams where you can push/pop
extra functionality into the data processing pipe. Having this on the
input and output side of things makes for a really flexible server. One
could filter the raw request, repair brain dead Accept headers, convert
from old protocols to new, set flags based on any header, uncompress,
decrypt.....

I think what's needed (2.0/3.0) is to make Apache more like self-contained
builing blocks where modules only know and care about themselves with a simple
Apache controller/scheduler that passes the request state from one module
to the next. At the moment the modules (IMO) know too much about
the core than they need to.

The great thing about streams is that the modules run concurrently so
data *flows* out of one module and into the next so multiple modules can
be processing the request at the same time. Does threads make such a model
feasible ?


dear Santa...



Mime
View raw message