Drive Realtime API今天改变了吗？ [英] Was the Drive Realtime API changed today?

问题描述

我有一个Realtime API应用程序，其中gapi.drive.realtime.CollaborativeString的原型被修改为提供额外的方法。今天（2014年10月30日）美国东部时间上午10点左右，该应用程序突然停止工作。事实证明，访问gapi.drive.realtime.CollaborativeString.prototype会引发错误，因为gapi.drive.realtime.CollaborativeString和所有其他Collaborative类现在都是未定义的！

我目前正在通过向每个CollaborativeString单独添加所需的方法来解决此问题，但如果Google Drive API小组中的某个人可以告诉我：

如果是这样，为什么？

最重要的是，为什么文档中没有警告或更改？除非没有变化，我只是很愚蠢，这导致了今天生产服务的重大停机。该文档仍然列出了gapi.drive.realtime命名空间中的类。

预先感谢您的澄清并对StackOverflow格式感到抱歉。也发布在Google云端硬盘问题论坛中。

解决方案

我们对API进行了一些更改，以避免暴露混淆的私有属性，这些属性导致了我们的几个用户使用自定义对象（ https://developers.google.com/drive /realtime/reference/gapi.drive.realtime.custom ）。

对于由此造成的停机时间，我深表歉意。我们不知道有人正在修改原型对象，事实上我们从来不会这样做（尽管显然它确实如此）。

我很乐意就您的应用进行一对一的对话，以及如何防止未来的宕机。我们有一个预发布频道，我很乐意将您列入白名单，以便您可以在之前测试更改，这些更改会影响您的制作用户。

I have a Realtime API application in which the prototype of gapi.drive.realtime.CollaborativeString is modified to provide extra methods. Today (October 30, 2014) at about 10 AM EDT, the app suddenly stopped working. It turns out that accessing gapi.drive.realtime.CollaborativeString.prototype throws an error because gapi.drive.realtime.CollaborativeString, along with all the other Collaborative classes, is now undefined!

I am currently working around this by adding the required methods to each CollaborativeString individually, but I would appreciate if someone on the Google Drive API team could tell me:

Has the API actually been changed today to remove the public handles for these classes?

If so, why?

Most importantly, why was there no warning or change in the documentation? Unless there was no change and I'm just being stupid, this caused significant downtime on a production service today. The documentation still lists the classes in the gapi.drive.realtime namespace.

Thank you in advance for your clarification and sorry for the StackOverflow format. Also posted in the Google Drive issues forum.

解决方案

We made some changes to the API to avoid exposing obfuscated private properties, which were causing problems for several of our users who were using custom objects (https://developers.google.com/drive/realtime/reference/gapi.drive.realtime.custom).

I'm sorry for the downtime that this caused. We did not know that anyone was modifying the prototype objects, and in fact we never doing so would work at all (though obviously it does).

I would be happy to have a 1-on-1 conversation about your app and how we can prevent future downtime. We have a pre-release channel that I would be happy to whitelist you for so that you can test changes before they affect your production users.

这篇关于Drive Realtime API今天改变了吗？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！