yep, I try to be fast in that
. And it affected my own installations, so the need for a solution was already there... And I really don't like to be somewhat responsible for people losing access to their sites - beta state or not.
No worries, the notifier does not
check on every request. Instead it only checks the current timestamp towards the saved one from the last notification. Only if the configured time is over (say 24h) the next steps are done - if necessary. Remote checks for updates have their own cache partitions, so this does not happen very often. This ensures that response times shouldn't be affected (not measurable so far).
At first I did have the notification beeing triggered OnManagerLogin. But this is imho quite useless: if you login, you will (hopefully) see the widget showing the update information right after that. No need to send out an extra email notification then.
Instead, if you haven't visited your manager for a while, my approach ensures that you still get informed about updates. Even with very low traffic on a site at least the googlebot triggers the notification check from time to time.
But you are right, I might filter the notification check as well on special pages to keep the impact even lower. It must only be ensured that the plugin is called on a regular base with a time span less than the minimum configured notification time. Maybe the googlebot together with a "hidden" page can be exploitet a bit more for that