I was reviewing the code in mod_rivet.c. If possible my purpose is to let the configuration handling be a little terser and make the configuration values readable from the scripting level through the RivetServerConf,RivetDirConf and RivetUserConf.
I noticed that some pointers to configuration scripts are stored in rivet_server_conf as Tcl_Obj* and others (namely pointers to before|after|error scripts) are referenced as simple char * pointers. I'll make their representation uniform as Tcl_Obj*. The treatment reserved to these objects keeps also open the possibility (even though of limited practical usefulness IMO) of embedding whole scripts in the apache confs writing multiple lines like RivetServerConf GlobalInitScript "line 1" RivetServerConf GlobalInitScript "line 2" ... RivetServerConf GlobalInitScript "line n" For a small project I was thinking also of creating a small Tcl extension the could allow ipc communication among apache children using shared memory. This would require an initial block of shared memory be created by libapr before apache forks. The hook run by apache after configuration loading and before forking is Rivet_InitHandler. I'd like to introduce a new configuration script to be run during this stage (ServerInitScript?). -- Massimo -- --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
