quote:
Originally posted by CookieRevised
An update checker should be powered by Plus! itself; Plus! will handle where to read from, where the update-db is located, what to show to the user, etc. All which is required in the script itself are 2 small extra tags (the numerical version number and the GUID), nothing more. The rest is in the update-DB.
That's the way i imagined it, except, the download DB would insert those values (ensuring the user didn't typo anything or used a non-unique ID). Scripters could optionally set a tag in their XML to disable autoupdate, should they want to use their own autoupdater they already created.
I don't really see a reason to provide autoupdate support to skins/scripts outside the DB. Not because it wouldn't be possible technically, but because Plus! in a way will be responsible for all skins/scripts that use autoupdate (they use the Plus! servers, Plus!' GUI will recommend the user to upgrade, etc.), while the quality of those downloads outside the db is hard to check... I can already imagine the posts "Plus! spreads virusses trough auto-update".
There would be a mutual benefit for submitting to the db: Developers get auto-update, users get more downloads to view at a central place and some type trustworthyness on the downloads distributed trough auto-update, i get an easier way to verify the downloads depending on auto-update.
In the end it's all up to Patchou, it's his software and servers being used for this. If he want's it, the possibillity is there, but i wonder who will be responsible for the unchecked downloads.
/ 
