Right now, there's an attribute in the "install" tag in the installer's XML file
("update_url"? Something like that). What it SHOULD be is a "update_url" tag in
itself that is a child of "install", so you can list as many URL-specifying tags
as you like, and have the updater go through each one, in order, until it
manages to pull the updates.txt file down.
At least, I think that'd be useful. unreal.epicgames.com was down for a few
hours, and everyone flipped their shit about not being able to update ut2003.
If this is too much infrastructure changing, even a "update-url2" attribute
would be handy, since the lesser likelihood of having two servers down
simultaneously would solve 90% of the problems.
--ryan.
This is actually not a big change for setup itself - we just get that
information and pass it over to setupdb to have it stored in the product's xml file.
The bulk of the changes would be done in setupdb itself, and also in other
programs that use that information, like loki_update, obviously.
Right now, there's an attribute in the "install" tag in the installer's XML file ("update_url"? Something like that). What it SHOULD be is a "update_url" tag in itself that is a child of "install", so you can list as many URL-specifying tags as you like, and have the updater go through each one, in order, until it manages to pull the updates.txt file down. At least, I think that'd be useful. unreal.epicgames.com was down for a few hours, and everyone flipped their shit about not being able to update ut2003. If this is too much infrastructure changing, even a "update-url2" attribute would be handy, since the lesser likelihood of having two servers down simultaneously would solve 90% of the problems. --ryan.