title: How do download accelerators work?
body: <p>We require all requests for downloads to have a valid login (non-http) and we generate transaction tickets for each download. If you were to go to one of the download links and attempt to "replay" the transaction, we use HTTP codes to forward you to get a new transaction ticket. This works fine for a majority of users. There's a small subset, however, that are using Download Accelerators that simply try to replay the transaction ticket several times.</p>
  
  <p>So, in order to determine whether we want to or even <em>can</em> support download accelerators or not, we are trying to understand how they work. </p>
  
  <p>How does having a second, third or even fourth concurrent connection to the web server delivering a static file speed the download process? </p>
  
  <p>What does the accelerator program do?</p>