public inbox for [email protected]
help / color / mirror / Atom feedFrom: Dave Page <[email protected]>
To: Magnus Hagander <[email protected]>
Cc: pgadmin-hackers <[email protected]>
Subject: Re: Somewhat excessive version checks
Date: Wed, 13 Jan 2021 09:02:29 +0000
Message-ID: <CA+OCxow+z9aW61irF41i-hWhBeWFSiimZNn+1TWFsdd6QNVfXA@mail.gmail.com> (raw)
In-Reply-To: <CABUevEzdC3hpNGqFQ_R6q=KD7wUYO+hesSV+fxee6ySNnVf90A@mail.gmail.com>
References: <CABUevEyMFa0ti59E0CkZfcNDdo6tgtX4PZcXqrK54KzKFfVCBA@mail.gmail.com>
<CA+OCxow7rQVSNhfhK_6E4KUX==P9BL2M_N4K7vSddD=nyMDhLA@mail.gmail.com>
<CABUevEzdC3hpNGqFQ_R6q=KD7wUYO+hesSV+fxee6ySNnVf90A@mail.gmail.com>
On Tue, Jan 12, 2021 at 7:50 PM Magnus Hagander <[email protected]> wrote:
> On Tue, Jan 12, 2021 at 9:57 AM Dave Page <[email protected]> wrote:
> >
> > On Mon, Jan 11, 2021 at 10:06 PM Magnus Hagander <[email protected]>
> wrote:
> >>
> >> Hi!
> >>
> >> If I read the code correctly, pgadmin will (unless turned off) hit the
> >> website to check the version.json file for updates *every time it
> >> starts*.
> >
> >
> > Every time the server starts, which is a little different, but still...
>
> Hmm. So one of us is definitely reading things wrong then :) I see it
> in the index() method, which has an URL router for / -- isn't that
> called for every time somebody somebody starts their browser to it?
> I'm not saying for every reload, but with a server install with 10
> users, won't it do it once for each?
>
> Or when is that actually called?
>
Huh, no you're right. It's a long time since I wrote that code :-/
>
>
> >> Wouldn't it make sense to rate limit that to checking say once per 24
> >> hours maximum? Or even 48?
> >
> >
> > That certainly wouldn't be a bad idea.
> >
> >>
> >>
> >> It seems nobody needs the update *that* quickly, and AFAICT it does
> >> call out to make that check synchronously on startup which means the
> >> user is waiting.
> >>
> >> And if/when doing that, it would be useful to include an
> >> If-Modified-Since header on the request, so the server can just
> >> respond with a tiny 304 reply when there is no update, which is going
> >> to be the majority of the time. Or possibly even more efficiently,
> >> create a custom etag and use If-None-Matches. If you make that etag be
> >> say the version that the client has, it becomes very cheap to check
> >> and you don't need to track any extra data.
> >
> >
> > Patches welcome!
>
> Hah, I clearly can't even figure out when the method is called :)
>
> And presumably you'd also want some place to store the state between
> calls, so you can keep showing the warnings about upgrades? Do you
> have state storage for such things arleady=
>
Yes - the SQLite config database. See pgadmin.model.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EDB: http://www.enterprisedb.com
view thread (6+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Somewhat excessive version checks
In-Reply-To: <CA+OCxow+z9aW61irF41i-hWhBeWFSiimZNn+1TWFsdd6QNVfXA@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox