CSMan
05-31-2002, 06:32 PM
I don't know if this is even possible, but I thought I would throw it out there and let you all tear it apart. :)
What if when there is a looming protein update, the day before it is supposed to happen, the new client is put up on the website and made available to auto-updaters.
Now I know the "old" protein and the new one can't be on the server at the same time. So what if, over that one day, people can autoupdate and when it goes to upload the completed work of the new protein the server says "not yet! Try again later." Thereby forcing them to no-net for a day.
During that day you could still have all the people working on the old protein able to upload their work and then grab the autoupdate. Then the next day the protein can be officially switched over and allow the new protein to be uploaded.
Seems like it could work to me, but what do I know!? :)
What if when there is a looming protein update, the day before it is supposed to happen, the new client is put up on the website and made available to auto-updaters.
Now I know the "old" protein and the new one can't be on the server at the same time. So what if, over that one day, people can autoupdate and when it goes to upload the completed work of the new protein the server says "not yet! Try again later." Thereby forcing them to no-net for a day.
During that day you could still have all the people working on the old protein able to upload their work and then grab the autoupdate. Then the next day the protein can be officially switched over and allow the new protein to be uploaded.
Seems like it could work to me, but what do I know!? :)