[HTTPS-Everywhere] Replacing the rulesets database file

[Red]

Accidentally did a direct reply last time.  Posting back to the list.

On 2014-08-11, 11:26 AM, Lunar wrote:
> (You have answered me privately, maybe that's what you wanted.)
>
> Red:
>> On 2014-08-11, 10:36 AM, Lunar wrote:
>>> Red:
>>>> The other problem is that the binary nature of rulesets.sqlite is
>>>> problematic for XHRs. When the file was fetched with a simple XHR, the
>>>> contents terminated after the SQLite version information at the
>>>> beginning of the file. When I asked in #extdev on mozilla's IRC network,
>>>> I was told I would have more luck downloading such a file using the
>>>> Downloads.jsm module, which you can see I started using in this commit:
>>>> https://github.com/redwire/https-everywhere/commit/92c765861cbf8a31c99507979ddee674b86b1e3d
>>> The SQLite database was introduced for performance reason. As users
>>> expect an update process to take time, how about downloading the rules
>>> in text format and loading them in the database as part of the process?
>> I like this idea. I could probably whip up a python script to transpile
>> the XML rules to JSON pretty quickly, have the extension fetch the JSON
>> rulesets with a good old XHR, and then run updates/insertions on the
>> entries in the JSON object. Does that seem more or less like what you
>           ^^
>          from?
>> had in mind?
> Sounds like it. :)
>
> The tricky part might be how to handle deletions (as always).
>


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 276 bytes
Desc: OpenPGP digital signature
URL: <https://lists.eff.org/pipermail/https-everywhere/attachments/20140811/1f080d12/attachment.sig>