rate-limiting support

Azure Devops includes rate limits that could be complex to predict in an automated solution. According to the documentation, the endpoints provide headers in responses in the instances that the client has hit a rate limiting threshold.

Is responding to the Retry-After header as discussed as recommendations in the API on the roadmap?

The API uses msrest as an HTTP library, which doesn't appear to support it at this time. Note, much of the Azure SDK uses azure-core which provides Retry-After support.

先查看 issue 中链接的 Azure DevOps 速率限制和 Retry-After 文档，然后检查客户端如何使用 msrest，并比较 azure-core 中对 Retry-After 的支持。明确预期范围是否为客户端级别的支持，并在实现前定义预期行为；done 应包括已达成一致的范围，以及对所选行为的覆盖。