PROPOSAL: schema for proxy superservice

[Francis J. Lacoste]

On Thu, Jan 17, 2002 at 12:27:02PM +0100, Joost van Baal wrote:
>  proxy/script/ms_proxy2dlf (should use Lire::W3CExtendedLog)
>  proxy/script/ms_isa2dlf (should use Lire::W3CExtendedLog)
>  proxy/script/squid2dlf (now in www/script/squid2dlf.in)
>  proxy/script/socks2dlf (now in socks/script/socks2dlf.in)
>  proxy/script/welf2dlf  (now in firewall/script/welf2dlf.in)

I would still keep a welf2dlf converter in firewall/script

Some information in WELF logs will be handled by the firewall
superservice other by the proxy superservice. 

Maybe it would be better to rename those services:

- welf_packet
- welf_proxy

> 
> We use the firewall superservice for pure packetfiltering, and the www
> superservice for pure webserver logs.
> 

I totally agree, but in the case of WELF logs you have packetfiltering
and proxy informations in that. I think the best thing is still to
process the log file two times (with both superservices).

-- 
Francis J. Lacoste
francis at Contre.COM
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
Url : http://lists.logreport.org/pipermail/development/attachments/20020117/df90d9d4/attachment.bin