h a l f b a k e r y"My only concern is that it wouldn't work, which I see as a problem."
add, search, annotate, link, view, overview, recent, by name, random
news, help, about, links, report a problem
browse anonymously,
or get an account
and write.
register,
|
|
|
I just saw Jutta's note in Meta > News about halfbakery's server being down.
The problem is, by the time you read things like that, the problem's been fixed---or else you couldn't read it. (It's like leaving a note for your spouse that says, "Honey, if you're reading this, I'll be home late...")
Instead,
how about having a down-time clearinghouse server somewhere for the specific purpose of listing all the websites that were down? You can't get through to your favorite site, so you check the clearinghouse, and aha---Jutta's apologizing for the latté she spilled into the UPS. It'd avoid the whole Catch-22, after-the-fact thing. (If the clearinghouse server went down, everyone else could post a note about it.)
[link]
|
| |
Pretty well baked in that - if a web site is going offline - http requests can be redirected by a simple DNS entry change. Whether or not a site owner chooses to do this or not is up the them. |
|
| |
[phoenix] but that doesn't account for the server going down suddenly |
|
| |
<smileydudette>Would you perverts stop saying "going down"</smileydudette> |
|
| |
[alx] True, but even that could be automated. I'm notified when one of my important servers stops responding to PINGs. There's no reason I couldn't run a script to update DNS if the downed server a web server. In fact, the more I think about it, the more I like it. |
|
| |
For what it's worth, I don't know of a product that does this now, but I haven't looked for one. |
|
| |