[squid-users] Squid 3 SSL bump: Google drive application could not connect

[Amos Jeffries]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2/01/2015 1:21 p.m., Eliezer Croitoru wrote:
> Hey Yuri,
> 
> You would want to avoid sqlite as far as you can due to it's Whole
> DB file LOCK nature.

Indeed. My experience with SQLite has been that it is vastly slower
than other DB options even a remote SQL database.

FWIW other Squid helpers written in C/C++ use BerkleyDB, and if
written in Perl use the DBI module for generic SQL DB's.

There is also the option of not using a DB at all in the initial
version. Squid has a cache of previous helper results which it uses
instead of calling the helper repeatedly for the same input.


Yuri, regarding Squid packaged helpers...

Distribution of any code within the Squid package requires:

 1) copyright under GPLv2+ or a GPL compatible license (such as Public
Domain, or BSD 3-clause license).

 2) compliance with the Squid coding and documentation guidelines.
  - One guideline is that the code be as portable as possible. So take
that into consideration with scripts.


* I also request authors/submitters of new helpers to please provide
at least 1 years support for it. Both in assistance of the community
here in squid-users learning how to use the helper, and in support
maintaining its code through its early period when most bugs are found.

Amos
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJUphGSAAoJELJo5wb/XPRj600H/i23sN/OgYocxWTAZ3/3lvM/
I/Z7KA/JTBCsVbWybO9WlNHZQkm9cE+F4H2a62Aw6MVojYERq7+p30/sB29GxGhS
05+JwpzvQ+bQfDgAi8fp4XPSnjuSBjA7MdQPUf6sAH8qFfOtuLYX3DBFKVGA77dY
mLxLsZcozJyqzMbwA55A4nU5sOBZo0je9LMdYXt0ag05RVVLRz4baGKKmZIH6rd2
HbZ5O2glTHhOv1UJ/oHoeX0LD3U1bg88iUD455/SEYwOgR56D0E6XfnK8MWYgYy7
7tsj1FkkVBxQKso6YT8+rD1czR1+eyQa4MT92nWMUBxsOmNifS4ujkhO1zZNIGQ=
=yJ2S
-----END PGP SIGNATURE-----