No it isn't difficult. It's like an array but with the safeguards for multi thread access. But that's not the point. If I create a command from a thread, which can not be executed from the :: namespace, it won't work in the rvt code neither.
What I see is that a shared lib loaded in a tclsh works perfectly, but not within the rivet environment. Maybe it is a limitation which could be explained. I started to look in the code, and found where the child process starts but the threads management is complicated. Is there a Rivet code documentation somewhere? Something which explains how rivet works and interact with apache and TCL ? Thank you, Brice. On Thu, Jun 14, 2018 at 11:36 AM, Massimo Manghi <massimo.man...@unipr.it> wrote: > Tcl threads follow an 'apartment thread' model. For what I remember > (never used extensively) each thread runs its own interpreter. That > means that namespaces are not inherited and have to be created when a > thread starts. Is the inter thread communication package so difficult to > use? > > -- Massimo > > On 06/14/2018 04:33 PM, Brice Hamon wrote: > >> Quick update: namespace route. >> >> I tried to import a namespace command from a namespace created in the >> RivetChildInit script into the TCL Thread and the import failed. >> That won't work either. >> >> So I think the closest to a solution was if the RivetChildinit vwait >> forever did not hang the web server, then this would work. >> >> >> >> > Firma il tuo 5 x mille all’Università di Parma e aiuta così i nostri > studenti che vogliono realizzare un’esperienza di studio all’estero – > Indica 00308780345 nella tua denuncia dei redditi. >
