Re^3: Paging with REST::Client?

just a shot in the dark, the server may be sending data keyed on "address" (10.20.30.40). In order to get to the next 500 results you have to use the last "address" you got from the last results page and send this as "start_addr".

sort of! In the link below, the server returns a reference to send it back to get the next page: perhaps you can figure it out by searching for paging in this page: https://ipam.illinois.edu/wapidoc/additional/sample.html?highlight=paging

Comment on Re^3: Paging with REST::Client?

Replies are listed 'Best First'.
Re^4: Paging with REST::Client? by Argel (Prior) on Jan 14, 2020 at 23:45 UTC
Nice guess at the third party app!! Looking at my confusing old code, I don't think the query/search needs to change. You just have to pass in _next_page_id from the previous query in as _page_id in the new query. I'm not 100% on that as I haven't looked at this code in several months and there's a reason I wanted to get away from having to manually do the paging. It really could benefit from an OOP approach, and I was hoping there was a module that already handled it. Elda Taluta; Sarks Sark; Ark Arks My deviantART gallery	[reply]
Re^5: Paging with REST::Client? by bliako (Abbot) on Jan 15, 2020 at 11:27 UTC
finally we are getting somewhere :) Now get cracking on that OOP approach and please post it (or any questions you may have) here. Glad it was of help.	[reply]