Replies: 1 comment 3 replies
-
Interesting.... I like the idea of a single call, but what's the time difference we're looking at? I mainly ask because most users will be running the script twice. Once for the "dry-run" to see what will happen, then a "real" run to commit. Could the initial "dry-run" API call be cached, then utilized by any follow-up script runs? Maybe utilize a timestamp to determine if the cache has "expired". Fresh caches get reused, but an expired cache causes a new fetch. Not sure... just thinking out loud... |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
There exists a place in the API to get a list of all current offerings.
Pros:
Cons:
5_100_257
bytes. A lot more information is transmitted than is strictly requiredI figure that if you plan to download an archive, then 5MB isnt too bad and that having to wait for multiple requests can be a bigger issue.
Thoughts? @Jaifroid @DocDrydenn
Beta Was this translation helpful? Give feedback.
All reactions