Wed Dec 19, 2012 11:33 am by will
ServiiGo is different as I download the music myself (unless it is a live stream) as I cache music on the device (and also prefetch the next track). I start writing into a file using a random access stream, once I have ~300KB or so I start playback by passing the partial file to the player. This all works fine if I know the exact content lenght/the server cleanly closes the connection when done as I can then finish and move onto downloading the next track in advance. However, because the connection is never closed and I don't know the content length, the method that reads from the music and writes it to a file will never stop. I guess I could estimate it based on bitrate and reported track length, but decided not to bother with hacky fixes as the server deals with it properly by using chunked encoding and closing the stream at the end in 1.1. I suggest you pm zip for beta access to 1.1, or wait as it should be due out very soon.