Confirmed users
657
edits
No edit summary |
|||
| Line 5: | Line 5: | ||
This is the approach where Firefox would download an update in the background, apply and install it alongside with the existing installation, and would then wait for the next startup. At startup, the firefox.exe stub would look for the existing installation directories, and would pick the newest one, and start up either by loading xul.dll and the rest of the libraries from that directory or by running a firefox.exe from that directory. After startup, when the next update arrives, the older version (which is not in use any more) will first be removed, then the new update will be applied and it will get picked the next time that Firefox starts up.<br> | This is the approach where Firefox would download an update in the background, apply and install it alongside with the existing installation, and would then wait for the next startup. At startup, the firefox.exe stub would look for the existing installation directories, and would pick the newest one, and start up either by loading xul.dll and the rest of the libraries from that directory or by running a firefox.exe from that directory. After startup, when the next update arrives, the older version (which is not in use any more) will first be removed, then the new update will be applied and it will get picked the next time that Firefox starts up.<br> | ||
: [[User:LawrenceMandel|LawrenceMandel]] The way I read this there will be two copies of Firefox on the system during an update: the currently running Firefox and a completely new, updated Firefox. Is this correct? Will this require twice the disk space? How much disk space are we talking about? Is this a concern? | : [[User:LawrenceMandel|LawrenceMandel]] The way I read this there will be two copies of Firefox on the system during an update: the currently running Firefox and a completely new, updated Firefox. Is this correct? Will this require twice the disk space? How much disk space are we talking about? Is this a concern? | ||
: (ehsan) Yes, we're talking about having two copies of Firefox on a system. This would require twice the amount of disk space (although we could resort to hardlinking on platforms which support it to reduce this). It would be an issue for mobile, except that mobile is completely out of scope here. I'm not sure if this is a concern with Desktop Firefox. | |||
=== Replacement approach === | === Replacement approach === | ||
| Line 13: | Line 14: | ||
#If the OS doesn't support removing files which are currently in use (Windows), the old directory should be marked to be removed during the next reboot and Firefox should check at start up to see whether the previous directory is in use, and if not it should move the new directory in place of the old directory and then restart. | #If the OS doesn't support removing files which are currently in use (Windows), the old directory should be marked to be removed during the next reboot and Firefox should check at start up to see whether the previous directory is in use, and if not it should move the new directory in place of the old directory and then restart. | ||
: [[User:LawrenceMandel|LawrenceMandel]] Do you mean reboot the OS or reboot Firefox? (I hope the latter.) | : [[User:LawrenceMandel|LawrenceMandel]] Do you mean reboot the OS or reboot Firefox? (I hope the latter.) | ||
: (ehsan) Reboot the OS. The user doesn't actually need to restart their system, the files will just stick around until that they do. FWIW, this is how all applications remove files which are currently in use on Windows. | |||
: [[User:LawrenceMandel|LawrenceMandel]] Eclipse's bundle mechanism supports the ability to register and unregister services with the software system. In this way an update can be applied to a running system without restarting the system. Even if the core executable required a different mechanism this may provide benefit as Firefox would not need to be restarted to update. Is there any way that we can update components of the Firefox system without restarting the system? | : [[User:LawrenceMandel|LawrenceMandel]] Eclipse's bundle mechanism supports the ability to register and unregister services with the software system. In this way an update can be applied to a running system without restarting the system. Even if the core executable required a different mechanism this may provide benefit as Firefox would not need to be restarted to update. Is there any way that we can update components of the Firefox system without restarting the system? | ||
: (ehsan) Not easily. We'd basically need to redesign everything from the ground up with that in mind. I think that's outside of the scope of this project (and to be honest I'm not sure if it's feasible). | |||
== Challenges == | == Challenges == | ||