Help
It came to light recently that DMZX's update URL (updates.digitalmzx.com) has been broken for a while. This caused issues for the 2.84 release. MZX itself should be more robust to failure of a single updater mirror, especially as we always have at least two copies of the data.
The updater could be modified to fall back to one (or more) additional repository URL if any file retrieval (particularly updates.txt) fails. This would mean the updater feature isn't compromised by failure of the primary mirror.
--ajs.
| Report ID | 468 | Title | Updater should have a fallback repository |
| Product | Archived Requests | Status | Implemented (Severity 3 - Medium) |
| Version | 2.84b | Fixed in | GIT |
Page 1 of 1
- Cannot start a new Issue
-
This issue is locked
Report ID #468: Updater should have a fallback repository
Page 1 of 1
- Cannot start a new Issue
-
This issue is locked
Replies (1 - 3)
#2
Lachesis 
- the pinnacle of human emotion
-
- Group: DigiStaff
- Posts: 3,895
- Joined: 17-July 04
- Gender:Female
- Location:Sealand
Posted 06 June 2012 - 09:08 AM
Updating status to: Implemented
Updating version to: 2.84b
Issue fixed in: GIT (debytecode)
Implemented in GIT master/baa3226 but has not been thoroughly tested. Basically now you can specify up to 16 update_hosts in the config file (hopefully nobody will ever need this many), or none and MZX will default to digitalmzx with devzero as fall-back #1 (albeit in-code, so the default bit will probably get canned soon in favor of trying to get everyone to update their config.txt...).
Updating version to: 2.84b
Issue fixed in: GIT (debytecode)
Implemented in GIT master/baa3226 but has not been thoroughly tested. Basically now you can specify up to 16 update_hosts in the config file (hopefully nobody will ever need this many), or none and MZX will default to digitalmzx with devzero as fall-back #1 (albeit in-code, so the default bit will probably get canned soon in favor of trying to get everyone to update their config.txt...).
"Let's just say I'm a GOOD hacker, AND virus maker. I'm sure you wouldn't like to pay for another PC would you?"
xx̊y (OST) - HELLQUEST (OST) - Zeux I: Labyrinth of Zeux (OST) (DOS OST)
w/ Lancer-X and/or asgromo: Pandora's Gate - Thanatos Insignia - no True(n) - For Elise OST
MegaZeux: Online Help File - Keycode Guide - Joystick Guide - Official GIT Repository
xx̊y (OST) - HELLQUEST (OST) - Zeux I: Labyrinth of Zeux (OST) (DOS OST)
w/ Lancer-X and/or asgromo: Pandora's Gate - Thanatos Insignia - no True(n) - For Elise OST
MegaZeux: Online Help File - Keycode Guide - Joystick Guide - Official GIT Repository
#3
Lachesis
- the pinnacle of human emotion
-
- Group: DigiStaff
- Posts: 3,895
- Joined: 17-July 04
- Gender:Female
- Location:Sealand
Posted 06 June 2012 - 09:09 AM
Issue fixed in: GIT
huh, it automatically added the "Issue fixed in" bit.
huh, it automatically added the "Issue fixed in" bit.
"Let's just say I'm a GOOD hacker, AND virus maker. I'm sure you wouldn't like to pay for another PC would you?"
xx̊y (OST) - HELLQUEST (OST) - Zeux I: Labyrinth of Zeux (OST) (DOS OST)
w/ Lancer-X and/or asgromo: Pandora's Gate - Thanatos Insignia - no True(n) - For Elise OST
MegaZeux: Online Help File - Keycode Guide - Joystick Guide - Official GIT Repository
xx̊y (OST) - HELLQUEST (OST) - Zeux I: Labyrinth of Zeux (OST) (DOS OST)
w/ Lancer-X and/or asgromo: Pandora's Gate - Thanatos Insignia - no True(n) - For Elise OST
MegaZeux: Online Help File - Keycode Guide - Joystick Guide - Official GIT Repository
Page 1 of 1
- Cannot start a new Issue
-
This issue is locked
0 User(s) are reading this issue
0 Guests and 0 Anonymous Users
Powered by IP.Tracker 1.3.2 © 2025 IPS, Inc.