Scott Laplante said:
> Our internal messages among different servers in our cluster are
> currently having to wait for a free connection thread, and in times of
> high traffic, this backup causes rather critical problems.
Not sure as I haven't used custom threads yet, but this is what I would
probably try: In init.tcl, you could start another threat. It seems to me
what you are doing doesn't require a pool of threads, so simple plain Tcl
server socket and non-blocking io should do the trick. Make sure this
thread doesn't exit on error and you can also have a scheduled proc
checking if it is still alive periodicaly.

Bas.


--
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.

Reply via email to