Community
Participate
Working Groups
Downloading and install of a very large product (500 meg and 130 features)is slow. Of course, Update is ultimately limited by the connection speed. We need to: 1) Ensure that our downloading algorithms are not slower than the equivalent functions in other applications using the same protocol (http). 2) Investigate if other protocols (ftp) can give faster download times 3) Review the task flow to see if we can do the install in the background so that the user does not have to wait until bytes are downloaded (background download). We can start the download in the background and move into the foreground (thereby blocking the UI) only when the byte moving part is completed).
Assigned to review the core part of the equation. Move to the UI for the rest.
Do some profiling time permitting.
Defer to 2.2 cycle.
We should investigate having the downloads done as a batch, using the Job mechanisms (a la automatic updates), and then install the features. Perhaps in 3.0.1 we have time to look at this.
*** Bug 271337 has been marked as a duplicate of this bug. ***
[LATER->WONTFIX] The "LATER" bugzilla resolution is being removed so reopening to mark as WONTFIX.