title: OVER_QUERY_LIMIT in a loop
body: <p>I'm getting the OVER_QUERY_LIMIT status code when using the Google Places Javascript Library. I have billing enabled on my account so it's not that I'm actually hitting the limit on the number of places requests I make, but I'm using the Javascript library and looping through a few hundred Places search requests. The problem is, this causes OVER_QUERY_LIMIT status to come back from the search unless, while debugging, I slow down the loop.</p>
  
  <p>Funnily enough this only happens with the JS Library, not when using the API directly. Rather than putting something in to slow the loop, is there anything that people can recommend to fix this?</p>
  
  <p>EDIT: More info on the two scenarios</p>
  
  <ol>
  <li>(the problem) Loops through dozens of points, each time making a places request through the official Places Javascript API</li>
  <li>(the one which works) Using node.js on the backend to make requests directly to the places search endpoint documented at <a href="https://developers.google.com/maps/documentation/places/" rel="nofollow">https://developers.google.com/maps/documentation/places/</a> and then pushing individual responses to the client.</li>
  </ol>
  
  <p>Thanks,
  Dan</p>