higher level api for batch requesting album info. #482
blueforesticarus
started this conversation in
Ideas
Replies: 1 comment
-
Other related ideas: the library should expose the limits for number of tracks/albums per endpoint as constants (I don't think checking them statically is a good idea though.) Having a cache for data may also be a good idea, although in this case I'd suggest having a trait so that application authors could integrate it into existing app db. There is also an issue of how to handle the possibility of stale data. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The tracks/albums api endpoints are essential for fetching info on a large number of entities.
However, code that needs to do this likely receives for data requests one by one, or in chunks different than the spotify endpoint max size.
This requires implementing a higher level api which maintains a queue of tracks/etc to query, a task to consume these and make the actual requests, and then feed the results back to the caller.
Implementing this in rspotify would save a lot of work for application authors and perhaps avoid performance issues where they would not otherwise bother to make use of the bulk api.
Beta Was this translation helpful? Give feedback.
All reactions