<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'><div style="text-align: left;">aka "The abomination that shall not be named"<br><br>Preparing for the bug-a-thon friday, I want us to come together on how we will write this out of the core; I think it will give us much better control over threading and deadlocking.<br><br>(The PROBLEM with the BlockingQueue is that threads might LOCK unknowingly because a sub-call felt like taking a peek at some blocking queue. Really really bad form.)<br><br>The BlockingQueue is used in the following contexts:<br><br>* Serving AssetRequests<br> - This should be solved with a specialized ThreadStart queue that news up threads whenever something tries to add to it or if there's something in the queue, up to a specified max of concurrent requests.<br><br>* The Packet Send queue<br> - This is up to discussion; how SHOULD sending work? Why do we even HAVE a global send queue? I guess that on a 'send' we should do a sweep thru the queues to see what else should be sent; and have one or several global timers sweeping thru all clients triggering sends on them? Or should we let the client thread take care of that?<br><br>* Texture and Asset downloads<br> - See AssetRequests<br><br>* JVMEngine Script compiling queue<br> - This is best commented on by the implementer...<br><br>I'm very motivated at doing this on friday, so give me your feedback ASAP, please.<br><br>Best,<br>Stefan<br></div></body>
</html>