1
Vote

Scrobble Queue persistence

description

Hey there,

We're currently using this very handy library downstream in the Elpis Pandora client's scrobbling implementation.

Sometimes scrobbles fail, and it'd be great if there was some way to preserve them until scrobbling is possible again, rather than just losing anything not yet scrobbled on program exit. For example Foobar uses a flat file to store a list of queued scrobbles in a persistent format, and works through that list.

comments

DanielLarsenNZ wrote Aug 2, 2012 at 9:49 AM

Hey mrmrpotatohead,

I'll take a look at this and get back to you.
  • DL

adammhaile wrote Aug 2, 2012 at 11:32 AM

mrmrpotatohead,

I'm the developer for Elpis. This would also likely be a good candidate for Elpis handling the persistence. Elpis is aware of failures to scrobble, but depending on the error message, it just throws them out and moves on (being that scrobbling is considered secondary to the function of the client). I will take a look at it from the Elpis side of things as well.

adammhaile wrote Aug 2, 2012 at 7:56 PM

Daniel,
I realized later that mrmrpotatohead is actually Ben, one of the contributing developers on Elpis.
I'm happy to give a hand at adding the persistance directly to LPFM should you deem it the proper place to put it. I just think it would make the most sense to allow for passing in a path to where the scrobble cache should go. But if you'd rather keep it out of LPFM, it can easily be added to Elpis as stated above.

-Adam

DanielLarsenNZ wrote Aug 4, 2012 at 12:02 AM

Yeah, my gut feeling is that this should be kept out of LPFM, but I will look and see if I can add a helper to make this easier.