home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Development
General Development (no feature request here!)
Need some change in the MP ISetupForm for webinterface
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="mPod" data-source="post: 52046" data-attributes="member: 11199"><p>Chili is right, I think. An example:</p><p></p><p>Package of Version 1</p><p>===============</p><p>fileA</p><p>fileB</p><p>fileC</p><p>fileD</p><p></p><p>Update package to Version 2 (only fileB has been changed)</p><p>====================</p><p>fileB</p><p></p><p>Update package to Version 3 (only fileB & fileC have been changed)</p><p>====================</p><p>fileB</p><p>fileC</p><p></p><p></p><p>So at the end we have the following files on the server:</p><p></p><p>Full Version 1</p><p>Full Version 2</p><p>Full Version 3</p><p>Update Version 1 -> 2</p><p>Update Version 2 -> 3</p><p></p><p>OR</p><p></p><p>Full Version 1</p><p>Full Version 2</p><p>Full Version 3</p><p>Update Version 1 -> 2</p><p>Update Version 1 -> 3</p><p></p><p>(But I think that is not that good, cause what happens if user starts with Full Version 2? This would mean we would also have to offer a package for Update Version 2 -> 3, could be that it all gets a bit much - although with some client/server intelligence it's all doable.)</p><p></p><p>I hope this makes sense, maybe you have some ideas to add here. But roughly that should be the idea. "Windows Update" is quite successful, so it can't harm to adopt some nice ideas from there (or other update systems).</p></blockquote><p></p>
[QUOTE="mPod, post: 52046, member: 11199"] Chili is right, I think. An example: Package of Version 1 =============== fileA fileB fileC fileD Update package to Version 2 (only fileB has been changed) ==================== fileB Update package to Version 3 (only fileB & fileC have been changed) ==================== fileB fileC So at the end we have the following files on the server: Full Version 1 Full Version 2 Full Version 3 Update Version 1 -> 2 Update Version 2 -> 3 OR Full Version 1 Full Version 2 Full Version 3 Update Version 1 -> 2 Update Version 1 -> 3 (But I think that is not that good, cause what happens if user starts with Full Version 2? This would mean we would also have to offer a package for Update Version 2 -> 3, could be that it all gets a bit much - although with some client/server intelligence it's all doable.) I hope this makes sense, maybe you have some ideas to add here. But roughly that should be the idea. "Windows Update" is quite successful, so it can't harm to adopt some nice ideas from there (or other update systems). [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
General Development (no feature request here!)
Need some change in the MP ISetupForm for webinterface
Contact us
RSS
Top
Bottom