[HTTPS-Everywhere] Draft specification for file used to check for ruleset updates

Maxim Nazarenko nz.phone at mail.ru
Wed Jun 11 02:43:18 PDT 2014

On 10 June 2014 18:47, Red <redwire at riseup.net> wrote:
> The subject of the db_version field was discussed at length in last
week's IRC meeting.  The conclusion of the conversation was that it would
be too much to expect developers to remember to bump the value of the
preference in the extension every time such a change is made.  My
understanding is that dealing with incompatibilities going forward will
handled more or less automatically by the fact that the extension would
reject ruleset releases corresponding to a newer version of the extension.
> So if HTTPS-E were modified in such a way that the ruleset database
format were to change, the extension itself would be receiving a version
upgrade (perhaps going from 3.5.1 to 3.5.2), in which case a client still
running 3.5.1 would not download a ruleset update with version 3.5.2.X
assuming they are on 3.5.1.Y.  When this scenario is encountered by a
client, we could even present the user with a message encouraging them to
upgrade the extension, keeping everyone up to date.

My understanding was that the db scheme change is a pretty rare event, and
one that requires a significant code overhaul. If the changes are frequent,
then tying the db format version with the extension version is much more
viable approach.

Best regards,
Maxim Nazarenko

P.S. I am not so sure about "please upgrade" message. The extendion does
update automatically by default.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.eff.org/pipermail/https-everywhere/attachments/20140611/7a67e292/attachment.html>

More information about the HTTPS-Everywhere mailing list