I am SICK and TIRED of these games that say "Unzip failed"
Or "Your network connection is not working
Or the hub server is down"
Or "Failed to download data (HTTP server returned unexpected status: 404 Not Found)"
If you aren't able to friggen download the game, then take the "download" link off! It's that simple. It's so friggen annoying to not be able to download anything.
ID:182173
 Nov 13 2008, 1:19 pm
|
|
Easier said than done. Sometimes these are a one-time problem (like the middle two). The others would require a ridiculous amount of bandwidth usage and processing power. The Staff would essentially have to write a program to go through all of the hubs and check that their download link would work, which would use up a freaking insane amount of bandwidth, considering they'd likely download a lot of working games.
Think about what you're saying before you make stupid suggestions, please. | |
Popisfizzy wrote:
(...)The others would require a ridiculous amount of bandwidth usage and processing power. The Staff would essentially have to write a program to go through all of the hubs and check that their download link would work, which would use up a freaking insane amount of bandwidth, considering they'd likely download a lot of working games. I do not support this feature request, but the concern you voice is not as hindering as you make it sound. Having a Cron Job run through each hub entry once a day/week is not that CPU intense. And considering bandwidth, the download can be stopped after the first TCP package is received, or even not try when the source is on BYOND itself. Even with an assumed 100000 HUB entries, that is very little resources used (if optimised). | |
Schnitzelnagler wrote:
I do not support this feature request, but the concern you voice is not as hindering as you make it sound. I was thinking the same. The only issue with doing it periodically is that games that are temporarily unreachable will not be available on the hub until the next check. So really we'd want to do the check when the page is loaded, perhaps cached every five minutes. | |
Tom wrote:
I was thinking the same. The only issue with doing it periodically is that games that are temporarily unreachable will not be available on the hub until the next check. Not a problem at all. Run a daily check and set a hidden "counter" for each hub. If the download fails, increase the counter by one. If the counter reaches 7, suspend the hub (as in notify owner and take the hub out of "downloadable" games, setting the download link to hidden). That way, you have seven separated control samples and a week seems to be a decent amount of time, both for a download problem to be fixed, as well as for a broken hub to be suspended. | |
Popisfizzy wrote:
The others would require a ridiculous amount of bandwidth usage and processing power. The Staff would essentially have to write a program to go through all of the hubs and check that their download link would work, which would use up a freaking insane amount of bandwidth, considering they'd likely download a lot of working games. You forget that lower-level languages than DM are quite fast. To loop through 1 million entries to check if the download link is still in working order, it would take a spare couple of minutes, possibly seconds (without the testing, just looping). You bring testing into that factor, you don't truly raise the bar all that much. As can be seen via the pager, the loop does not have to download working games at all--it can tell when there is a 404 error. As far as the "Unzip Failed" message goes, that could take a while. I would try to make a program that tests this upon creation of the hub entry. Think about what you're saying before you make stupid suggestions, please. Be nice! | |
And why are you posting this in BYOND features of all things? This is more of a personal problem really.