With the support of Windows and threaded MPMs the command [pid] ceased
to provide a unique identification of an execution thread. On windows
Apache logs both the pid and the thread id are printed in the error log
lines but for debugging purposes I needed to have this information
printed also on the browser. The immediate workaround is to require
package Thread and call [::thread::id], still I started to like the idea
that Rivet could get access this information without the need to depend
on an external package (with the purpose of calling a single command)
I prepared an initial simple version of a ::rivet::thread_id command the
returns an hexadecimal representation of what apr_os_current_thread
returns. Currently I didn't pay attention to compatibility with
::thread::id but I'd like to have your opinion
-- Massimo
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org
For additional commands, e-mail: rivet-dev-h...@tcl.apache.org
