Topic c4u Update System
This board is threaded (i.e. has a tree structure). Please use the Reply button of the specific post you are referring to, not just any random button. If you want to reply to the topic in general, use the Post button near the top and bottom of the page.
In Response to Newton
To optimize for the last one is probably the better way for OC because it hopefully means less maintenance for us.
I think you have a point regarding the masterserver. To have the logic in the masterserver is also better because this way, we are able to change the update infrastructure centrally, not individually in every client. The update request would look as easy as: Client sends version information, masterserver replies the link to the destined update package.
Of course, this means that some more initial work has to be done. Thats why I suggest that the update system will be kept very simple in the first versions:
client sends version information, masterserver always points to the newest complete installation. That saves the effort to implement any logic in the masterserver.
I think you have a point regarding the masterserver. To have the logic in the masterserver is also better because this way, we are able to change the update infrastructure centrally, not individually in every client. The update request would look as easy as: Client sends version information, masterserver replies the link to the destined update package.
Of course, this means that some more initial work has to be done. Thats why I suggest that the update system will be kept very simple in the first versions:
client sends version information, masterserver always points to the newest complete installation. That saves the effort to implement any logic in the masterserver.
Powered by mwForum 2.29.7 © 1999-2015 Markus Wichitill