<!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><FONT face=Arial size=2>I have created a new page on the wiki, outlining
the threading strategy, or lack thereof.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2><A
href="http://opensimulator.org/wiki/OpenSim:Threading_strategy">http://opensimulator.org/wiki/OpenSim:Threading_strategy</A> </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>I think we should streamline our use of threads. I
am especially concerned about the way threads are used in the ClienView, where a
thread is used per client. One thread per connection is <EM>the</EM> classical
way of handling several clients connecting to a single server, unfortuantely
this frequently leads to a scenario where hundreds, if not thousands of threads
execute in one process. I would suspect that the user, asset and grid servers
will have a large number of connections, consequently we need to think ahead,
and plan for good scalability in those server modules.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>I would propose that we generally switch to a
strategy similar to the one used in BaseHttpServer, relying on the thread pool.
</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>/tleiades</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV></BODY></HTML>