<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.6000.16525" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Hi</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV>> How would the thread pool help ? IMHO the threads should be
per-region, not per-client - then the number of threads would be quite
limited.<BR><BR><FONT face=Arial size=2>Ok, I can see that I may not have been
clear in my communications, sorry about that. What I was trying to say was that,
IMO is this:</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>1) I think that the current codebase, having a lot
of different strategies for handling threading is makes the code harder to
read.</FONT></DIV>
<DIV><FONT face=Arial size=2>2) That Threadpools, were designed into the .NET
framework, to assist in creating multithreaded applications, without introducing
the overhead of an application having a lot of threads (creating, </FONT><FONT
face=Arial size=2>destroying and switching threads)</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>To my knowledge, each application domain has a
separate threadpool, consequently I believe that the threadpool is a per-region
thing.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>/Tleiades</FONT></DIV></BODY></HTML>