[Mod-guile-devel] Questions ...

[rm]

Hi Dale,

just diggin' my ways through mod_guile.c again. 
What is the rationale behind the following defines:

#define HANDLERS 0
#define GBRL     1
#define CHILD    1
#define CONFIG   1

it looks to me as if at least CHILD and CONFIG could/should
be activated all the time.

Your version of 'make install' (that i copied over to
'Makefile.in' makes the DSO module executable - why?

You declare your Apache configuration commands as type
'OR_ALL', saying that such configuration options can show
up _anywhere_ in the configuration file. I'd suggest to make
them RSRC_CONF which would declare them to be valid only in
server global places (i.e. _not_ in <Location> or <File> sections).

I currently work on a mg_guile_handler that takes a module and
an (optional) handler name that can be configured on a per-
File or per-Location basis. Since this will cause a growth of
line of codes i'm thinking about splitting up mod_guile.c into
several files. What do you think about moving the req_record stuff
into a seperate file (and possibly into its own module) ? 

 Ralf