Background Updates/Implementation Strategies: Difference between revisions

Jump to navigation Jump to search
No edit summary
Line 10: Line 10:


#If the OS supports removing files which are currently in use (*nix), it would just remove the existing installation and move the new directory in place of the old one.  
#If the OS supports removing files which are currently in use (*nix), it would just remove the existing installation and move the new directory in place of the old one.  
#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 startup 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]] 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?


== Challenges  ==
== Challenges  ==
Confirmed users
2,473

edits

Navigation menu