[GH-ISSUE #22] Cache metadata and audio keys #11

Closed
opened 2026-02-27 19:28:16 +03:00 by kerem · 3 comments
Owner

Originally created by @sashahilton00 on GitHub (Jan 29, 2018).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/22

Issue by plietar
Wednesday Dec 30, 2015 at 12:03 GMT
Originally opened as https://github.com/plietar/librespot/issues/19


Metadata and keys should be stored in cache as well, in something like an sqlite database.

Originally created by @sashahilton00 on GitHub (Jan 29, 2018). Original GitHub issue: https://github.com/librespot-org/librespot/issues/22 <a href="https://github.com/plietar"><img src="https://avatars0.githubusercontent.com/u/1489775?v=4" align="left" width="96" height="96" hspace="10"></img></a> **Issue by [plietar](https://github.com/plietar)** _Wednesday Dec 30, 2015 at 12:03 GMT_ _Originally opened as https://github.com/plietar/librespot/issues/19_ ---- Metadata and keys should be stored in cache as well, in something like an sqlite database.
kerem 2026-02-27 19:28:16 +03:00
Author
Owner

@sashahilton00 commented on GitHub (Jan 29, 2018):

Comment by plietar
Wednesday Mar 16, 2016 at 04:21 GMT


Audio keys are now cached (85903a0).
Metadata isn't yet.

<!-- gh-comment-id:361257234 --> @sashahilton00 commented on GitHub (Jan 29, 2018): <a href="https://github.com/plietar"><img src="https://avatars0.githubusercontent.com/u/1489775?v=4" align="left" width="48" height="48" hspace="10"></img></a> **Comment by [plietar](https://github.com/plietar)** _Wednesday Mar 16, 2016 at 04:21 GMT_ ---- Audio keys are now cached (85903a0). Metadata isn't yet.
Author
Owner

@sashahilton00 commented on GitHub (Feb 1, 2018):

@plietar given that it's a connect implementation (always online), and metadata is fairly lightweight, is it worth the trouble?

<!-- gh-comment-id:362128712 --> @sashahilton00 commented on GitHub (Feb 1, 2018): @plietar given that it's a connect implementation (always online), and metadata is fairly lightweight, is it worth the trouble?
Author
Owner

@sashahilton00 commented on GitHub (Mar 22, 2018):

Closing this as a non-issue. librespot is primarily a connect client in it's current form, thus metadata caching is semi pointless when it's always online. In the event that it is being used as a library by another program, each program's requirements will be different, and thus the optimal caching strategy will likely differ between projects, and should be left up to them to implement. What's important is that librespot provides the interface for metadata retrieval. Closing, can be reopened if there is disagreement with this.

<!-- gh-comment-id:375159301 --> @sashahilton00 commented on GitHub (Mar 22, 2018): Closing this as a non-issue. librespot is primarily a connect client in it's current form, thus metadata caching is semi pointless when it's always online. In the event that it is being used as a library by another program, each program's requirements will be different, and thus the optimal caching strategy will likely differ between projects, and should be left up to them to implement. What's important is that librespot provides the interface for metadata retrieval. Closing, can be reopened if there is disagreement with this.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/librespot#11
No description provided.