title: Right way to "timeout" a Request in Tornado
body: <p>I managed to code a rather silly bug that would make one of my request handlers run a very slow DB query.  </p>
  
  <p>Interesting bit is that I noticed that even long-after siege completed Tornado was still churning through requests (sometimes 90s later).  (Comment --> I'm not 100% sure of the workings of Siege, but I'm fairly sure it closed the connection..)</p>
  
  <p>My question in two parts:
  - Does Tornado cancel request handlers when client closes the connection?
  - Is there a way to timeout request handlers in Tornado?  </p>
  
  <p>I read through the code and can't seem to find anything. Even though my request handlers are running asynchronously in the above bug the number of pending requests piled up to a level where it was slowing down the app and it would have been better to close out the connections.</p>