Anything whose life cycle spans the lifetime of a child process can in principle be set up in RivetChildInitScript. In case the process termination leaves something behind that needs some clean up you can put these tasks in a RivetChildExitScript.
-- Massimo On 07/19/2013 10:44 PM, Brice Hamon wrote: > Hi Massimo. > > Thank you for your answer. I looked for a variable/array but I didn't > think looking at the ::rivet::load_env as I thought it was only for > global usage. Cool working. > > Yes you are correct and after trying to understand what this fireevent > issue was I thought I will be also in the same situation. > > No I don't think my TCL api will work on a single threaded interpreter > as the C++ side is totally MT but I can try. Else I will follow this bug > resolution/patch/hack to make it work. > > Other than that bug, creating all DB/external connection in the > RivetChildInitScript is the correct choice right? > > Thank you again, > > Brice. > > > -- -- Massimo Manghi Dipartimento di Neuroscienze Unità di Biofisica e Fisica Sanitaria via Volturno 39 43125 Parma --------------------------------------------------------------------- To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org For additional commands, e-mail: rivet-dev-h...@tcl.apache.org
