Folks, this is nothing really special, just a way to allow keeping "track" of previous versions and being able to "rollback" ASSP in case of issues
Here's the idea; at the moment ASSP checks for newer versions and downloads them into the "download" folder and then, if configured to do so, updates the current running ASSP Now, my idea is to add a little twist to the above, let's say ASSP upon startup will create (if not existing) a folder called "versions", at that point the updater mechanism will do the following: check for a new version online, and, if a new assp.pl exists: * download assp.pl to the "download" folder * copy the current assp.pl into the "versions" folder renaming it as assp-vv.vv.vv-rr.rr.rr.pl that is, for example "assp-2.0.1-2.0.12.pl" * optionally (if configured to do so) copy the new assp.pl from download over the running assp.pl and restart this way, during time, the "versions" folder will carry all the previous versions *installed* on the system and it will be easy to rollback to the previous version (or to an older one) in case of need; I think this feature may be particularly useful for "beta" versions which gets updated quite often ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test