是否可以修剪Microsoft graph API返回的skiptoken/deltatoken的长度 [英] Is it possible to trim the length of skiptoken/deltatoken which is returned by microsoft graph api

查看:68
本文介绍了是否可以修剪Microsoft graph API返回的skiptoken/deltatoken的长度的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

当前,当我在/users/delta, 响应中返回的增量令牌的长度为3k个字符.

Currently when i do GET on /users/delta, the delta token returned in the response have a length of 3k characters.

ince 我的应用程序在保存此令牌值时有长度限制.

Is there a way to reduce the length? since my application have a length restriction while saving this token value.

除了某些时间戳映射详细信息之外,此skiptoken还携带哪些信息.有没有办法解码此令牌?

What information does this skiptoken carries, other than some timestmap detail. Is there a way to decode this token?

shahabas

推荐答案

你好感谢您的查询.

Skiptoken用于在查询任何Odata服务时控制结果的分页.如果您选择实施此方法,则客户通常需要知道总体上有多少个结果.要查找您的条目总数你可以追加 您查询的

Skiptoken is used for controlling pagination of results while querying any Odata service. If you choose to implement this, the client usually needs to know how many results there are , as a whole. To find out total number of entries you  you can append the


inlinecount 选项.例如,如果您要查询包含5000个条目的用户列表,则图Odata服务无法一次返回5000个条目,因此存在 为每个查询设置的限制(以保持API和Graph Odata服务后端的效率和更好的性能).因此,您可以分页请求以每次获得500个条目. (对于MS Graph,您可以使用
inlinecount option to your query. For example if you are querying user list which contains 5000 entries so the graph Odata service cannot return 5000 entries at once hence there are limits which are set for per query (so as to maintain efficiency and better performance of the API and the Graph Odata service backend). So you can page the request to get 500 entries every time. (For MS Graph you can use


top 以获得最大页面大小. /em>),那么对于每个这样的块,您都可以获得一个skiptoken以及结果,该结果将包含有关您需要从何处再次读取数据的书签 . Skiptoken包含有关正在查询的下一个条目集合的信息.我们认为此长度不能减少,因为Odata服务会自动创建该长度(在本例中为Graph API后端).您可以阅读有关此内容的更多信息 此处.
top to get the max page size . ) For every such chunk you can then get a skiptoken along with the result which will contain the bookmark as to where you need to read the data from again . Skiptoken contains information about the next collection of entries which are being queried. We do not think this length can be reduced as its automatically created by the Odata service, ( in this case Graph API backend). You can read more about this here .

希望所提供的信息有所帮助.如果这可以帮助您解决问题,请将其标记为答案,这样可以增加答案的针对性,并使社区更容易找到答案.如果您还有其他疑问,请随时让 我们知道.

Hope the information provided helps. In case this helps you with your problem please mark it as answer so that the relevance of the answer is increased and its easier for the community to find this . In case you have any further queries , feel free to let us know. 

谢谢.


这篇关于是否可以修剪Microsoft graph API返回的skiptoken/deltatoken的长度的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆