Hi Scott
I guess that any thread that has to be launched before requests are
served must be created within the ChildInitScript by executing something
like
set ::my_thread_id [::thread::create <script>]
::thread::preserve $::my_threads_id
ChildExitScript (which should work with the lazy bridge for now) should
be the place where you can stop threads adopting the usual good practice
for nudging threads into releasing resources and then exit
With this approach you would have an extra private thread for each rivet
thread but I wonder if this is what you really want since you're
outlining something like a monitoring thread.
-- Massimo
On 1/29/24 21:03, Scott Pitcher wrote:
Thank you Massim. I haven't used ChildExitScript, but I do have a question.
I want to run a thread that looks after a session database, and possibly
others if the method works. Where would be the best place to start a
persistent thread from? I thought about just launching a thread and
using the global namespace to record it's existence. But is there a
better way of doing this?
Kind regards,
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
