Oh, I think we kind of misunderstood each other a bit - at the moment its not possible to retrieve these mentioned plugins latest online version from the internet
(as only totalcmd.net is supported & they aren't uploaded there), hence the "
Unknown." status for both of them.
Honestly, it wouldn't be a hard job to include the latest version number of at least some exotic plugins inside the TU executable, but my original plan from the beginning was to not do it. It would have the same weak points:
- should always be around keep checking if the embedded latest available version numbers are still accurate or not
- what if the user decides not to update his/her Total Updater instance, thus keeping an old version database that leads to false informations about available updates
So basically yes, I wrote a module that manages to query the totalcmd.pl subpages you also collected above, and as of now it works just fine - the only problem is that it takes about ~6-7 seconds
(with 5Mbps connection; currently its not async) to get and process all these data, and this is mostly for
nothing - after comparing & merging the totalcmd
.net and
.pl ones, the result would be that most of the
.net plugins in fact are newer than the other, so the prolonged query was actually unnecessary.
I am now thinking on the following possible solutions:
- a) Continuing the current idea & make the request asynchronous (would still mean a somewhat longer update search)
- b) As totalcmd.pl seems to be abandoned, just one-time query the current list of its plugins & embed the result into the TotalUpdater executable (+45 kB) by pairing their ID with the current ones in the database (to make possible the comparement of their version with the .net ones)
- c) As totalcmd.pl seems to be abandoned, just one-time query the current list of its plugins & save a local file with the result by pairing their ID with the current ones in the database (to make possible the comparement of their version with the .net ones)
- d) Put a tiny little script on a stable server (e.g. something like "http://totalupdater.com") that could grab all possible source of plugin versions, so it could be the only page that Total Updater queries (it could also be a script that runs once/twice a day and writes info to a file on the server, so TU could just grab it instantly everytime)
- e) Update some version numbers on totalcmd.net (like "AviWcx" which points to "1.9", but still listed as "1.5"), and upload some abandoned plugins from totalcmd.pl to totalcmd.net - the only problem with the latter could be in case the license/readme file forbids to do so, not sure about the other cases (no license/readme/etc...)
I would be glad to hear your opinions.
Regards,
Bluestar