我一直在寻找在 Google Documents List Api 中更快地访问不同页面的方法，为此，我希望能够从列表的特定部分开始下载，即如果用户有 400文档，能够从文档 300 开始下载。但是我现在意识到 start-index 参数不再起作用（请参见此处 http://code.google.com/apis/documents/changelog.html #release-Version-3.0 ）
是否有人找到了一种无需使用 feed.getNextLink() 方法即可访问用户文档列表的不同部分的方法？我会使用这个，但你每次都必须下载他们文档的第一部分，这毫无意义。
我查看了 getNextLink 返回的 url，其中包括“？开始键=EAIaUAsSADpKEGQhvg7_ZoxPRJQo76P_9gVCNX__AP8AOPDQpn_HysvGyszNyszNy8fRzsvRjMesq9LKqry2ms2ttJacoMyxvM_Sy4j_AP_-SAIMIgsJgFkvD8cAAAAgBg”
我调查过，但事实证明这不能自己生成，而是在服务器端生成（请参见此处：http://code.google.com/apis/apps/profiles/developers_guide_protocol.html#retriving_with_query ）
因此，任何人都可以方法来做到这一点？
I have been looking for ways to gain access to different pages more quickly in the Google Documents List Api, and to do this I'd like to be able to start my downloads at a specific part of the list, ie if a user has 400 documents, be able to start downloading at document 300. However I have now realised that the start-index parameter no longer works ( see here http://code.google.com/apis/documents/changelog.html#release-Version-3.0 )
Has anyone found a way to access different parts of a user's documents list without using the feed.getNextLink() method? I would use this but you have to download the first part of their documents each time making it pointless.
I have had a look at the url returned by getNextLink and it includes "?start-key=EAIaUAsSADpKEGQhvg7_ZoxPRJQo76P_9gVCNX__AP8AOPDQpn_HysvGyszNyszNy8fRzsvRjMesq9LKqry2ms2ttJacoMyxvM_Sy4j_AP_-SAIMIgsJgFkvD8cAAAAgBg"
which I investigated, but it turns out this cannot be generated yourself, and is generated server-side ( see here: http://code.google.com/apis/apps/profiles/developers_guide_protocol.html#retrieving_with_query )
So, anyone have a way to do this?
发布评论
评论（1）
目前，无法在文档列表 API 上执行基于索引的查询。必须使用下一个链接对结果进行线性分页。
不过，从 API 获取一组资源后，您可以使用新的 更改 feed 以使该设置保持最新，而无需重新查询整个设置。
Currently, there is no way to do index-based queries on the Documents List API. Results must be paged through linearly using next links.
However, once you've fetched a set of resources from the API, you can use the new Changes feed to keep that set up to date, without the need to requery the entire set.