Walter Ian Kaye wrote:
If I create my own log files (via CGI) for other users to download and
process with their tool of choice (likely analog?;), should I generate
them tab-separated for easy importing (like into Excel) or
space-separated like CLF? Or should I make it user configurable?
[I'm gonna write a banner ad thingie, and advertisers will want to
know stuff.]
Excel is probably not a very useful tool for analyzing log files. It has
significant limitations on rows, columns and data size and I don't think
it provides many tools useful for counting. Excel would seem to me to be
more useful with summaries where it can be used for cross-tabs (pivot
tables) which it's very good at.
I would recommend using W3C Extended Logfile Format as it's
self-documenting and is supported by most log-file analysis tools. See
http://www.w3.org/TR/WD-logfile.html
And/or... can I call analog from a CGI on particular log files such
that I could display stats for users automatically?
Analog has a forms interface that you can deploy to allow users to run
their own reports. See http://analog.cx/docs/forms.html
And if so, can I create my own HTML templates for analog's output?
Analog can export to XML format or it's own proprietary
computer-readable format which you can post-process into any HTML you
wish. You might check out http://timian.jessen.ch/ for an XML processing
tool and http://reportmagic.org/ for an HTML post-processor with some
customization.
--
Jeremy Wadsack
Seven Simple Machines
+------------------------------------------------------------------------
| TO UNSUBSCRIBE from this list:
| http://lists.meer.net/mailman/listinfo/analog-help
|
| Analog Documentation: http://analog.cx/docs/Readme.html
| List archives: http://www.analog.cx/docs/mailing.html#listarchives
| Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
+------------------------------------------------------------------------
