Bugzilla – Bug 10455
New SP connecting to SbS won't get immediate firmware update
Last modified: 2011-01-14 13:01:10 UTC
If a user connects a new Controller for the first time to that server, the firmware is checked and the latest firmware is downloaded. They may therefore get stuck with old and possibly incompatible firmware on a device for a long time. If the user doesn't disconnect/reconnect the player, the firmware gets downloaded to the server but the user doesn't get offered the update. I suggest that we: 1. Offer the user the firmware update immediately upon checking the version from the network, while it's still downloading. 2. Give the user progress indication while it's downloading from the Internet as part of the upgrade process.
Dean do you think we need this for 7.4?
One easy solution might be to give SP the URL from SN if the download is not complete.
Dean - is this still an issue? AFAIK SC is checking for new firmware every 12h, then signalling the Controller its availability when done. No need to disconnect/re-connect.
The only solution I could come up with was this: 7.4 officially supports 2 SP products: Jive, Baby We hardcode these 2 products to download version files for at startup. When one of these connects and calls Slim::Utils::Firmware->url we already know the right version and can construct the download URL immediately, while also triggering the real firmware download in the background that gets cached to the updates folder. Pros: Immediately firmware update. Cons: This results in the user's internet connection downloading the same file twice at the same time, resulting in an even slower update and more load on our servers. I suppose we could delay this download by some amount of time to try to avoid this dual-download. Will have to keep this hardcoded list updated when we release a new product. Unannounced products wouldn't be able to be placed in this list, and would work like they do now. Going to punt on this for now unless someone has a better idea or really thinks we need to do this.
moving current p2 bugs to p3 to make room for moving p1.5 bugs to p2
Administrative move of 7.5 bugs. All P2, P3, P4 being downgraded one level. Will then split P1s.
Moving P3 and lower bugs to next release target