|
|
Post by vincent0607 on Apr 25, 2024 3:30:39 GMT
From redfish spec v1.20, introducing a new query parameter $skiptoken from chapter "9.6.12 Next link (Members@odata.nextLink) property"
After took a look, still didn't understand that what is differences between $skiptoken and $skip, and how to use this $skiptoken
Could you help explain more that? thanks
|
|
|
|
Post by mraineri on Apr 25, 2024 11:47:48 GMT
The difference is $skiptoken is an opaque token that the service generates to track collection pages from client requests. It's entirely up to you if you want to use a skiptoken versus echoing other query parameters the client used in the next page link; both would behave identically. How you generate it and track it internally is entirely up to you. For example, the client's original request could be something like... GET /redfish/v1/SomeCollection?$filter='Color' eq 'Red' In the response, the next page link might contain "/redfish/v1/SomeCollection?$skiptoken=213498732549". When the client then performs "GET /redfish/v1/SomeCollection?$skiptoken=213498732549", it'll go to the next page for the original "GET /redfish/v1/SomeCollection?$filter='Color' eq 'Red'" request. Here are some useful links to how it works in pure OData environments, which is where this is derived: * learn.microsoft.com/en-us/odata/webapi/skiptoken-for-server-side-paging* community.sap.com/t5/technology-blogs-by-members/difference-between-skip-and-skiptoken-in-odata/ba-p/13560047 |
|
