a home for squid2dlf

[Joost van Baal]

Hi,

I started hacking on squid2dlf, as contributed by Joost Bekkers.  I am
wondering wether it would be sane to (keep) this under the www
superservice.  squid logs stuff like:

  979992041.366 502 192.168.1.160 TCP_IMS_HIT/304 216 GET
         http://example.com/home2.html - NONE/- text/html

This has some similarity with www.xml; it might be wise to use the
extension mechanism.  However, the difference might be too big.  We miss
"referer", "useragent", "gzip_result" and  "compression".  We'd have to
add "elapsed", "cache_result_code", "servername" and "ident".  (See the
just commited squid2dlf manpage for description of these fields.)

I find it hard to make a sane guess at what would be the best choice:
keep with www, or define a new superservice like e.g. "proxy".

Anybody a clue?

Bye,

Joost

-- 
Joost van Baal              . .           http://www.logreport.org/
                           .   .
/^LogReport$/               . .               joostvb at logreport.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.logreport.org/pipermail/development/attachments/20011114/f9e2a58f/attachment.bin