ProgMaster wrote on 31
st Jan, 2008 at 10:55am:
Quote:<!---
var refreshID = "";refreshID = setTimeout ("DoRefresh ()", 180000);
function DoRefresh () {
document.location.href = 'playing.php?buster=30110745921';
}
Is tha refresh-time based on how long the current track is going to last? If not, try to find out if you can make it work that way, it'll save a lot of refreshes and thus bandwidth.
Yes, the script is based on the length of the current track and refreshes automatically as the track changes. If left open by the user, it'll also refresh itself periodically.
If the refresh is indeed the 180000 as expressed in milliseconds, it is always 3:00 minutes. It doesn't change.
If it is the `buster' value, I have no idea how to interpret that
From the playlist:
11:49:15 Pendragon - Wishing Well (d. Two Roads)
11:43:46 Pendragon - Wishing Well (c. We Talked)
11:37:00 Pendragon - Wishing Well (b. Sou' By Sou' West)
11:32:30 Pendragon - Wishing Well (a. For Your Journey)
11:29:41 Noah - Take Me Back
From my log:
12:45:47 3:00 15 Pendragon - Wishing Well (c. We Talked)
12:48:49 3:00 15 Pendragon - Wishing Well (c. We Talked)
12:51:50 3:00 15 Pendragon - Wishing Well (d. Two Roads)
12:55:03 3:00 32 Camel - Summer Lightning
12:58:09 3:00 32 Camel - Summer Lightning
13:01:11 3:00 15 White - Fate
The leftmost time-stamp is the local time I fetched the playlist, the second is the delay I read (always 3:00)
Quote: Quote:BTW, the script is very very easy to modify for other stations and/or groups of like/dislike.
Sorry, I've no idea what this means ...
*my* script is easy to modify