[Playlist] Update++;

[Chris Anderson]

The simple answer is just to provide a 1:1 correspondence between
tracks and images, and use the track's image element to hold the image
url. I guess that doesn't fit into your application exactly.

I hadn't pondered the ability to provide more images than tracks, and
to have them change more often than tracks. In which case using your
player to correlate the image xspf and the track xspf seems like the
best way to do it.

The gold standard for practical xspf implementations has for a long
time been Fabricio Zuardi's player. If your content works on it, then
you are ready to reap all the benefits of xspf.

http://musicplayer.sourceforge.net/

I'm not sure how to approach providing images as essentially a
seperate feed. In the case of your application, I now realize that
they aren't even best thought of as associated with individual track
elements, but are really a parallel stream.

-- 
Chris Anderson
http://jchris.mfdz.com