谷歌日历停止对json rpc和api-java-client的支持 [英] google calendar discontinuing support for json rpc and api-java-client

问题描述

我们使用Google API Calendar v3，Google表示他们将停止对json rpc的支持

We use Google APIs Calendar v3 and Google said that they'll discontinuing support for json rpc Discontinuing support for JSON-RPC and Global HTTP Batch Endpoints.

我找不到他们是否计划兼容v4版本或当前版本是否兼容.文档没有对此进行参考. Java快速入门

I cant find if they plan a v4 version compliant or if the current version is compliant. Documentation don't reference about it. Java Quickstart

关于此的任何信息吗?

推荐答案

不仅仅是影响日历的日历，它影响的所有Google API发现API.批处理端点

Its not just Calendar that is effected its all Google APIs discovery APIs that are effected. The batching endpoint

POST /batch HTTP/1.1
Authorization: Bearer your_auth_token
Host: www.googleapis.com
Content-Type: multipart/mixed; boundary=batch_foobarbaz
Content-Length: total_content_length

将在2019年3月25日左右停产.也就是说，我怀疑客户端库已全部更新以将其删除.我是其中两个的贡献者，并且还没有听说要从库中删除批处理功能.

Will be discontinued around March 25, 2019. That being said i am skeptical that the client libraries have all been updated to remove it already. I am a contributor on two of them and haven't heard anything yet about removing the the batching ability from the libraries.

Google API客户端库已重新生成，不再能够 向全局HTTP批处理终结点的请求.使用这些的客户 库必须升级到最新版本.客户未使用 Google API客户端库和/或对JSON-RPC进行自定义调用 端点或HTTP批处理端点将需要进行概述的更改 在下面.

Google API Client Libraries have been regenerated to no longer make requests to the global HTTP batch endpoint. Clients using these libraries must upgrade to the latest version. Clients not using the Google API Client Libraries and/or making custom calls to the JSON-RPC endpoint or HTTP batch endpoint will need to make the changes outlined below.

全局批处理终结点为

www.googleapis.com/batch

www.googleapis.com/batch

新的是

www.googleapis.com/batch/<api>/< version>

www.googleapis.com/batch/<api>/<version>

我认为这里选择的单词不正确，如果需要，它们会重新生成.更改不会影响用户，只有一个例外.由于端点是特定于API的，因此异类批处理请求单个批处理请求，而该批处理请求中包含一个以上的API将无法正常工作.

I think the choice of words incorrect here and it they will be regenerated if needed. The change should not effect users with one exception. That being heterogeneous batch requests a single batch request containing more then one API within the call wont work due to the fact that the end point is API specific.

现在，就我所知，这是个坏消息，没有什么可以替代它了.您将无法发出异构批处理请求. Google API Java客户端库似乎使用了旧的终结点

Now for the bad news to my knowledge there is nothing that is going to be replacing it. You will not be able to make heterogeneous batch requests. The Google apis java client library appears to use the old endpoint BatchRequest.java so if you are using heterogeneous batching your going to have to change your code by the time they update the library to support the new API specific endpoint.

更新

在过去的24小时里，我与Google进行了很多次来回交流，因此我对该帖子做了一些澄清.

After a lot of back and forth with Google over the last 24 hours I have gotten some clarification on that post.

1. 分批处理仍可与客户端库一起使用
2. 大多数客户端库似乎已经在使用此端点，因此不应进行任何更改.
3. 您将只能在批处理请求中调用一个API.例如，您不能在同一批处理请求中调用驱动器和日历API.您将必须进行两个批处理请求，一个用于驱动器，另一个用于日历.

该帖子可能会进行一些编辑，以使语言更加清晰.

There may be some edits coming to that post to clear up the language a little to be more clear.

我已经更新了答案，以反映Google的澄清

I have updated my answer to reflect the clarifications from Google

这篇关于谷歌日历停止对json rpc和api-java-client的支持的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！