919755 - [music] In media remote controls, split up the "update metadata" and "update duration" events

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::Music, defect)

Description

[Jim Porter (:squib)]

Right now, we emit an "update metadata" event when we 1) change songs, or 2) update the duration of a song. This can be confusing for downstream listeners, since there's no surefire way to tell if we started playing a new song or if we just updated the duration. (If you're thinking about detecting a new song by checking if the artist/album/title are different, remember that some files have no metadata.)

I propose we split these events apart: one for updating the metadata when we play a new song, and one for updating the duration. This would also simplify sending album art, since we wouldn't have to worry about flooding the connection with album art blobs when the duration is changed.

Note: I don't think we need this for 1.2, since things are ok right now, but this would be a nice simplification for 1.3 and beyond. We definitely want to get the API locked down by the time we open up the Inter-App Comms API to non-certified apps so that we're not causing problems for third parties.

Comment 1

[Jim Porter (:squib)]

Given that we'll be moving to the Media Controller API one day, I don't think we need this.