{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 戒情不戒烟 的问题《Is youtube data api paging consistent if you use p》','https://www.manongdao.com/q-245051.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
The YouTube V3 Data API provides "page tokens" for paging result sets from search endpoints.
Is the dataset being viewed consistent if you make use of the page tokens?
e.g. if there is an ordering on view count, which is likely to change with time, then is the ordering over the total result set guaranteed across multiple queries, so the lowest result on the first page is guaranteed to be ordered greater than the highest result on the following page?
The ordering is not guaranteed when using page tokens. (Nor was it guaranteed when using start-index in v1/v2.) If something changes with the backend data source's ordering in between fetching one page and the next page, then retrieving the next page would reflect the updated ordering.