Hi Valery, 

it seems the Rivet development has been finally resumed. 
I'm glad to hear that you have ideas, plans and will to
get involved on this.

I had an email exchange with David about Rivet and
the next step to take in its development. We agree
that providing a working support for apache2 in
non-threaded mode is a priority (also called pre-fork
as I learned last night). I think I can be
involved in doing it also as a way to become familiar
to the Apache API. I presumably can dedicate time on
this starting with the end of the next week, after
i have settled some businesses. 

Keep in touch 

  -- Massimo

On Fri, 31 Aug 2007 11:44:06 +0300, Valery Masiutsin wrote
> Hello, David !
> 
> 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. 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.
> 
> Regards Valery
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


--
Universita' degli Studi di Parma (http://www.unipr.it)


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

Reply via email to