I want all of the You Don't Know Jack games redone in HD. I'd take them on PC or console. They would make excellent downloadable content. And yes I've heard the rumor of a new version for Wii. I'll likely own that as well, but playable versions of all of the old content would be epic.
First off, by and large the entities you speak of do not own the broadcast affiliates. They may air their content on them a few hours a week (20-30 hours) but the rest of the content is determined by the owner of the station(s). As for up time, if your job does not include maintaining the application the server is running, and you can ping it, then you're doing your job and it's up. It's a matter of perspective. The end user may see it as down time, but not on your watch. The "server uptime" would be fine. The application is another matter. As for a broadcaster, maintaining a signal is the engineer's uptime. If some other equipment is faulty, that too could be included. However, if it is something related to traffic, then engineering wouldn't be accountable. I'll even play devil's advocate and say that the operator on duty should catch any issues, but even then if traffic made an error not much can be done.
When you see black or any other interuption it is not down time. That could be a snafu, but unless it goes completely off (white snow) the broadcaster is putting out signal. Think of it as a DVD player on but not playing a DVD. Uptime for television broadcasters is in the range of 99.999%
I want all of the You Don't Know Jack games redone in HD. I'd take them on PC or console. They would make excellent downloadable content. And yes I've heard the rumor of a new version for Wii. I'll likely own that as well, but playable versions of all of the old content would be epic.
First off, by and large the entities you speak of do not own the broadcast affiliates. They may air their content on them a few hours a week (20-30 hours) but the rest of the content is determined by the owner of the station(s). As for up time, if your job does not include maintaining the application the server is running, and you can ping it, then you're doing your job and it's up. It's a matter of perspective. The end user may see it as down time, but not on your watch. The "server uptime" would be fine. The application is another matter. As for a broadcaster, maintaining a signal is the engineer's uptime. If some other equipment is faulty, that too could be included. However, if it is something related to traffic, then engineering wouldn't be accountable. I'll even play devil's advocate and say that the operator on duty should catch any issues, but even then if traffic made an error not much can be done.
When you see black or any other interuption it is not down time. That could be a snafu, but unless it goes completely off (white snow) the broadcaster is putting out signal. Think of it as a DVD player on but not playing a DVD. Uptime for television broadcasters is in the range of 99.999%