I have successful implementation of static players on many of my sites using iframes. This has served my purposes thus far, and has been a little complex to make happen. i often have needed to pass a 'frame' state through a GET variable in php. a client of mine has been having display issues on their part, and it would be nice to see urls showing up in the address bar, which now brings me to rethink my approach.
In looking at Beatport's source for their html5 player, it seems they are using a javascript instantiated player, which looks very dissected and precising. So... are they keeping track of the player state and passing these variables from one page to another? what is their platform? php w/ ajax? node.js? ruby? is this asynchronous i/o at work? or just coolness afforded by html5's audio object? this is something i would like to understand, as i may have to reposition my whole method for future applications.
furthermore, does the soundcloud player api spit out progress locations? any help is greatly appreciated.