On 2004.08.17, Robert Seeger <[EMAIL PROTECTED]> wrote: > Rather than implement thread pools in pure Tcl, why not just expose AS' > thread pool implementation at the Tcl level? That way, in the end, > there's only one code base to test and update. > > Keep in mind, I'm not saying its better, I'm really just curious.
Yes, that would be the longer-term solution. However, to prove it's worth investing in the longer-term solution, implementing thread pools in pure Tcl would hopefully try to "prove" that having such a thing would solve one of the bottlenecks to otherwise pure Tcl solutions. If, upon implementing thread pools in pure Tcl, we found that performance was still insufficient in a pure Tcl implementation, we'd know that it's not worth exposing AOLserver's C implementation with a Tcl interface. However, if the contrary is found to be true, then yes, we'd work to abstract out AOLserver's thread pooling and expose it with a Tcl API. If we're lucky, we do it in a backwards-compatible fashion as a bonus ... -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
