google-maps-api-3 - OVER_QUERY_LIMIT 详细信息

Question

Google map 在某些情况下会返回 OVER_QUERY_LIMITS 状态。我正在寻找有关这些条件的任何详细信息。

我可以通过在延迟后重新提交路线服务路线请求来处理状态。通过使用多个“魔数(Magic Number)”setTimeout 延迟管理和限制请求，我已经能够最大限度地减少 OVER_QUERY_LIMITS 状态的数量。我担心虽然这些“神奇数字”在我的机器上为我工作，并且在设置它们的当天我所在位置的网络连接，但它们在其他情况下可能是合适的。

有没有人有解决 OVER_QUERY_LIMIT 问题的经验，尤其是使用不受上述任何影响的自适应策略？

编辑-------------------------------------------- ------------------------

看来问题还不是很清楚。我找到并理解了在线文档。问题是关于它的含义、细节是什么以及处理它们的策略。特别是:

什么是“每秒有多少个请求”？是 1 还是 5 还是 50 还是什么？它是如何确定的？它对什么有反应？它如何随使用而变化？

哪些策略，尤其是适应性策略，似乎可以解决这个问题？

再次编辑:可能还是不太清楚。 ------------------------------------

在路线服务请求的特定情况下:

• 有谁知道“每秒请求数”的实际值是多少？
• 有谁知道这个值是常量还是会变化？
• 有谁知道它是否改变了影响改变的因素？
• 有谁知道在做另一件事之前需要等待多长时间方向服务请求？

更一般地说，有谁知道这些与其他谷歌地图服务有何变化？

Answer 1

Google 的服务受配额和速率限制(取决于服务器负载)。

From the documentation on OVER_QUERY_LIMIT in the web services

Usage limits exceeded

If you exceed the usage limits you will get an OVER_QUERY_LIMIT status code as a response.

This means that the web service will stop providing normal responses and switch to returning only status code OVER_QUERY_LIMIT until more usage is allowed again. This can happen:

• Within a few seconds, if the error was received because your application sent too many requests per second.
• Some time in the next 24 hours, if the error was received because your application sent too many requests per day. The time of day at which the daily quota for a service is reset varies between customers and for each API, and can change over time.

Upon receiving a response with status code OVER_QUERY_LIMIT, your application should determine which usage limit has been exceeded. This can be done by pausing for 2 seconds and resending the same request. If status code is still OVER_QUERY_LIMIT, your application is sending too many requests per day. Otherwise, your application is sending too many requests per second.