| Summary: | [plan item] Improve update manager downloading | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Jim des Rivieres <jeem> |
| Component: | Update (deprecated - use Eclipse>Equinox>p2) | Assignee: | Dorian Birsan <birsan> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P4 | CC: | amanji, celek, jasper.chui.rh, manahan |
| Version: | 2.1 | Keywords: | plan |
| Target Milestone: | 3.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Jim des Rivieres
Once we move to jdk1.4 builds we can look at using the new java io package (java.nio.*) for faster, asynchronous downloads. Currently we are downloading plugins in parallel, by feature only. That is, features are downloaded sequentially, and within each feature, plugins are downloaded on multiple threads (5). Withing the same eclipse session all the successfully downloaded features/plugins are cached, so if downloading fails half-way through, if the install process is restarted, downloading will resume from where it was left off. This is only true at the feature/plugin granularity level. If a very large plugin has been partially downloaded before the download failure, then the plugin will be re-downloaded from the beginning. proposed for 3.0 - JDK 1.4.1 dependency 3.0 Update provides restartable http downloads. Parallel downloading turned out to not improve things in any significant way and has been dropped. There is also support for mirroring remote sites locally (inside the enterprise) and have users update/install from the local network. |