Re: [squid-users] access-lists from mysql ?

Ah...But is it floating on the web to be found by Google? ;) I
searched off and on a little for a way to easily tie Squid to MySQL
and I found lots of people asking but very little practical examples
beyond user authentication using the supplied demo script.

I'm curious how much caching would really be necessary in the helper
program though given that Squid already caches external ACL lookup
results on its own. I haven't seen any slowdown using this on my own
LAN, but that's a fairly small traffic sample.

My end goal was something using as few external library dependencies
as possible in a compiled language, so I can say I achieved that at
least. I really was just tired of the whole process of: ssh, su, edit,
reload, test -- each time I needed to block a new domain one of my
kids stumbled on ;) The SQL tie-in is also nice because it can be
managed by so many different tools so you can create portal pages or
small GUI tools to allow less technical users to update their lists
without worrying about what file on disk to edit and what commands to
run afterwards.

Every solution will have pros and cons, just have to pick the best one
for your own use case :)

On Sat, Feb 2, 2013 at 11:42 PM, Eliezer Croitoru <eliezer_at_ngtech.co.il> wrote:
> Hey Matthew,
>
> I wrote a more complex solution like that in ruby with MYSQL, TOKYOCABINET,
> REDIS and some others.
>
> I have just seen couple days ago another a very nice interface with a very
> nice api called "moneta" for ruby.
> It uses one interface for couple DB such as mentioned above.
>
> Until now I have used BDB, MYSQL, POSTGRESQL and the mentioned above.
> The problem with SQL DB are the size of the DB and speed compared to the
> others.
> TOKYOCABINET takes about 50% from MYSQL in any store there is for a simple
> HASH DB.
>
> I know people like sql queries but sql DB are very slow for computing stuff.
> The more accurate you are the more speed you get.
>
> Eliezer
Received on Sun Feb 03 2013 - 06:02:45 MST