[TC9b2] Check for udates doesn't recognize new beta 3

[petermad]

The Check for updates feature doesn't detect the new TC9b3 version

[wanderer]

Yup. Noticed it too and posted here.

This happens in b2 and it may be related to the respective change shown in history.txt

Code: Select all

17.06.16 Added: Update checker: Use DNS TXT record if available, lookup of A record only if TXT record lookup fails (32/64)

[petermad]

Hmm, I dont get "hosts=null" with TC9b2 - it just claims that TC is updated despite the new beta 3

[ghisler(Author)]

Please check this reply:
http://ghisler.ch/board/viewtopic.php?p=311167#311167

[petermad]

I can confirm that beta 3 correctly recognized the new beta 4 version when manually checking.

[petermad]

I can confirm that beta4 correctly automatically recognized the new beta5 version

[wanderer]

I can confirm that beta4 correctly automatically recognized the new beta5 version

Well, i cannot confirm your confirmation because i was notified for b5 by your post in this thread! That's what i call instant notification! Let's throw the updater away.

[ghisler(Author)]

The auto-updater isn't meant for people who constantly look for new versions. It only checks once every 24 hours, and will notify only once to not annoy the user too much. So if you update to a newer version too quickly, you will not get the notification at all (since you already knew that there was an update).

[Lefteous]

2ghisler(Author)

will notify only once to not annoy the user too much

A very good point in time to notify the user is when starting TC before the normal UI is displayed. When this is done the following choices would make sense:
- Download now
- Remind me later
- Skip this update

[petermad]

How about reminding of new updates every time TC is started, but provide the alert with a checkbox: "Don't notify me any more until next update"

[wanderer]

It only checks once every 24 hours

That statement is probably not accurate. If TC is run on Sunday at 20:00, a new version is released on Monday at 11:00 and then TC is used on Monday at work hours, the user will actually get a notification on Tuesday. And all that just to avoid a single DNS hit to check the version? OK, doing that every time TC is executed is probably a waste of bandwidth (from the provider's point of view) but the check could take place not at the next TC startup after 24 hrs but after 4 or 6 hrs. We're talking about what, 200K DNS hits per 6 hrs? Would that cause a problem?

P.S. If that's too much, how about every 12 hrs?

[Sob]

On the other hand, TC is updated only rarely (beta tests excluded).

So if a new version is released a year after last one, who cares if some users get notified up to 25 hours later (worst case with current check once a day and one hour TTL on DNS record)? Previously they would notice who knows when, maybe a month later, maybe a year later, ... just when they'd remember to check the website manually.

And even with current more frequent betas, it's still no biggie. Either you're really interested, in which case you check the forum daily anyway, or you can surely survive if you find about new version a day later. Final version won't come out so fast that you wouldn't have a chance to report your bugs. :)

[wanderer]

2 Sob

You got a point there. Perhaps the interval could be configurable with a minimum of 24hrs (or more?) for stable versions and 4 hrs for betas.