> I am interested in adding limited NWS (mod_neowebscript) compatibility to 
> rivet.
> At the moment I am studying rivet internals and apache API,
> trying to outline the way a NWS compatibility layer should be implemented.

If I may ask - how much NWS code do you have?  Perhaps Damon and Karl
can comment, but I think you would be better off moving to Rivet at
this point - that, or simply reviving the NWS code (which is still on
sourceforge, I believe).  Making a compatibility layer just doesn't
buy you that much.  That said, if you want to do it, no one's stopping
you - although there are no guarantees it will be included.

> Here is what I have come up with:
> 1. I think there should be an option in virtual host configuration file,
> something like "RivetUserConf NwsCompatibilty Yes".
> I will check for its existence in Rivet_InitTclStuff() and use a modified
> version of Rivet_PerInterpInit()  -> Rivet_NwsInterpInit().
> This is where I will initialize low level nws core commands.

> 2. Also a NWS version of Rivet_SendContent() -> Rivet_SendNwsContent()
> will be implemented.

> 3. Also I am going to restructure things a bit, for a example
> during its initialization, mod_neoscript tries to initialize plenty of tcl
> extensions (neosoft extensions, tclx, pgtcl, gdtcl), i think all this stuff
> should be moved to nws specific init.tcl.
> I am really puzzled with the question of how to get values of
> RivetUserConf variables during the initialization phase. All I see in
> rivet is using them during request processing, rivet_user_vars is
> empty during initialization. Will appreciate any pointers to
> documentation/module sources/etc, which will clear things up.

You want to look at this function:

static const char *
Rivet_ServerConf( cmd_parms *cmd, void *dummy, char *var, char *val )

Ciao,
-- 
David N. Welton
http://www.welton.it/davidw/

DedaSys LLC
http://www.dedasys.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to