title: OVER_QUERY_LIMIT details
body: <p>Google Maps returns status of OVER_QUERY_LIMITS under some conditions.  I'm looking for any details on what those conditions are.</p>
  
  <p>I'm able to deal with the status by resubmitting the Directions Services route request after a delay.  I've been able to minimize the number of OVER_QUERY_LIMITS status by managing and throttling the requests with several 'magic number' setTimeout delays.  I'm concerned that while these 'magic numbers' work for me on my machine with my network connection at my location on the day they were set they may be in appropriate under other circumstances.</p>
  
  <p>Does anyone have any experience with addressing the OVER_QUERY_LIMIT issue particularly with adaptive strategies not susceptible to any of the above?</p>
  
  <p>Edit ---------------------------------------------------------------------</p>
  
  <p>It seems that the question might not be entirely clear.  I found and understand the online documentation.  The question is about what it means, what the details are, and strategies for dealing with them.  In particular:</p>
  
  <p>What is "to many request per second"?  Is it 1 or 5 or 50 or what?  How is it determined?  What does it respond to?  How does it change with use?</p>
  
  <p>What strategies, particularly adaptive strategies, seem to work for dealing with the issue?</p>
  
  <p>Edit again: Perhaps it's still not clear. ------------------------------------</p>
  
  <p>In the particular case of a directions services request:</p>
  
  <ul>
  <li>Does anyone know what the actual values are for 'request per second'?</li>
  <li>Does anyone know if the value is a constant or if it changes? </li>
  <li>Does anyone know if it changes what affects the change? </li>
  <li>Does anyone know how long a wait is necessary before doing another
  directions services request?</li>
  </ul>
  
  <p>More generally, does anyone know how these change with other google map services?</p>