I'd actually like the synchronisation thing to be happening in the background as you worked.

Sure, it would lag behind what you were doing at the time. But you probably spend more time editing the playlist and putting new songs in than you do waiting for it to download, yeah?

Sure, it might have to change something it's already written. So what? It's not like you're paying for the bandwidth.

I know it's more complex coding, but I see it as just a transaction queue; the emplode front end puts commands into the queue and the back end does each item in the queue as it finishes the last. And you could also save that queue in a file on the hard disk so that if it crashed you could simply continue on from where you were up to last - a 'resume' feature if you will.

Rob? How possible is that?

Save the whales. Feed the hungry. Free the mallocs.