On Fri, 2008-02-15 at 10:12 +1100, Robert Collins wrote:

> What I meant was that when an eCAP module needs (say) DNS access,
> there will be someone looking at the ease of use of the DNS interface
> in squid. And just that act will provide some pressure to improve
> things.

With option #1 (expose everything), somebody can use the existing DNS
code/API in Squid "as is". They do not have to clean it up to use it
because they have access to everything Squid code has to offer (and that
code already uses DNS, of course).

With option #2 (the eCAP library layer), the developer may indeed have
to polish Squid code to provide DNS functionality to modules that do not
have access to raw Squid guts. I am not saying this will happen all the
time, but I think it will happen more often because there is an external
pressure/limits that force a cleanup.

This is all hand-waving and speculation, of course.



Reply via email to