The Thread_Dispatch function already hides the master's thread ID in
data(master_thread)
where data is the socket-related state array. So, if you do the
upvar #0 Httpd$sock data
hack, then you have access to this information.
>>>Colin McCormack said:
> Hi,
>
> May I make a suggested addition to lib/thread.tcl?
>
> In Thread_Start, around line 113, it would be most useful to have something
like:
>
> Thread_Send $id \
> [list set pid [thread::id]]
>
> So that each of the worker threads could access the parent's functionality.
>
> Alternatively, could threadmgr have a command to send a script to the master
_thread for processing.
>
> The problem I'm trying to solve is one in which I'm using a web interface to
control a single process, the process is maintained (in some sense) by th
e master thread, and so it's necessary to have that master thread arbitrat
e between accesses by the worker threads.
>
> Which do you think is the better approach?
>
> Colin.
>
>
-- Brent Welch <[EMAIL PROTECTED]>
http://www.ajubasolutions.com
Scriptics changes to Ajuba Solutions
scriptics.com => ajubasolutions.com
