On 12/21/2007 01:37 AM, Christopher Woods wrote: > Static content can be cached and distributed to > local nodes by ISPs and the BBC itself, but realtime NTP queries will really > kill a box and suck up a ton of bandwidth.
But NTP would be a mad way to get a clock on a web page roughly right. Web servers know what the time is (or they ought to), so one of them could provide a clue in a header or a variable or a comment or something that the clock could be told when it started up. There's enough dynamic content on the page to attach the time to without much of an additional load on anything, and all without having to open up another series of tubes to time servers. And by the way, I do agree with the sentiment that if you put a ticking clock on a BBC page, the time it shows ought to be within an egg-boiling interval of dear old Green Witch. Mean time, I also appreciate that this is a nostalgic touch, but I don't lose sight of the meaning of a BBC clock to Mr and Mrs Punter. -- Frank Wales [EMAIL PROTECTED] - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/[email protected]/
