rahul wrote:
>
> This FastTrack proposes the integration of Squid Cache 2.6.STABLE16[1]
> as a component in sfw stack.
This is just a nit, but I'm a fan of assertive voice in functional
specs. Right now this is an early draft so it is indeed a proposal but
eventually after reviews & approvals it will become final so it's more
convenient to write it that way from the very beginning. So instead of
saying, for example,
"This FastTrack proposes ..."
I like to write
"This project delivers ..."
Like I said, a nit...
> /etc/squid/squid.conf.default
> /etc/squid/mime.conf.default
> /etc/squid/msntauth.conf.default
> /etc/cachemgr.conf
Are these the working names of the files? Or samples? As with the
apache discussion, squid should deliver a working configuration such
that it'll work out of the box as soon as admin enables the squid
service.
Is there anything under /var? On my Linux box I see a /var/spool/squid/,
do we need this as well?
> 2.2. Versioning
>
> The Squid follows a simple development model. The development and
> stable versions coexist. There are three tags used to indicate the
> state of a version. STABLE, PRE and DEVEL.[3]
> DEVEL is the version that undergoes active development and addition
> of features. When it matures it is tagged PRE as beta after which it
> is tagged STABLE when the release approaches stability.
>
> There are two active versions in existence now. Squid 2.6.STABLE16 and
> Squid-3.0.PRE6. This case deals with Squid 2.6.STABLE16 alone.
> ( Referred to by Squid in the rest of this document)
>
> 6. Packaging and Delivery
>
> We propose to package squid under SUNWsquid. Multiple versions
> coexisting on the same machine is not anticipated since this is not
> a development platform, and general usage pattern is to have a single
> instance.
>
> 7. Squid Interfaces
>
> 7.1. Interface Stability
>
> The Squid project has not changed the configuration file format from
> the time it started. It is a plain text file with space separated key
> and values. However, newer configuration keys and values have been
> added in the releases.
>
> Squid does not support loadable modules. Thus binary compatibility is
> not relevant for Squid.
(I grouped the above sections since they address the same issue.)
So can we assert that future squid versions will very likely continue
to be config and interface compatible? In other words we can continue
updating the versions through patches and there won't be any of the
issues faced by apache & php? That's nice, simplifies everything..
> 2.3 Modules
>
> The modules are compiled statically into Squid, thus each release of
> Squid needs to recompile the modules that it supports.
So unlike apache, there is no notion of user-generated modules then?
> 4. Squid Documentation.
>
> Squid comes with generic documentation in man page format for squid.8
> cachemgr.cgi.8, squid_db_auth.8, ncsa_auth.9, squid_ldap_auth.8,
> pam_auth.8, squid_unix_group.8 and squid_ldap_group.8. These will be
> placed in the /usr/squid/man/man8 directory as done by the canonical
> distribution.
Some other components deliver a stub manpage in the system location,
which points to the component-specific manpages available in the
above location. (For example /usr/share/man/man1/php.1 for php).
> 7.2. Imported Interfaces
>
> Squid imports interfaces from
Here the spec needs a reference to the ARC case where each imported
interface was defined and make a note in the table of the stability
classification the exporting case used.
> Solaris Trusted Extensions library (libtsol)
Can you expand on this? squid will depend on TX?
> In addition, the following external Interfaces is imported:
>
> SMCdb (BerkeleyDB4.2 libdb-4)
> SMCsasl (SASL2 libsasl2)
I guess the db dependency is gone, right?
> ================================================================
> Addendum 1: Squid Integration Directory and File Structure.
>
> 1. The following files are included in the Squid integration:
> /usr/squid
...
> etc
> squid.conf.default
I assume this is:
/etc
(i.e. it's not under /usr/squid)
--
Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
