By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
429,084 Members | 1,969 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 429,084 IT Pros & Developers. It's quick & easy.

Webalizer

P: n/a
Hi!

Why should or shouldn't we use Webalizer?
How different is Webalizer compared to webstats services like
onestat.com?

Remko

Oct 9 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
bo********@gmail.com wrote:
Why should or shouldn't we use Webalizer?
Don't know ... what does this have to do with writing HTML for the World
Wide Web?

--
-bts
-Motorcycles defy gravity; cars just suck
Oct 9 '06 #2

P: n/a
bo********@gmail.com wrote:
Hi!

Why should or shouldn't we use Webalizer?
How different is Webalizer compared to webstats services like
onestat.com?
Webalyser analyzes your Apache logs - all your accesses, 404s, 302s etc.
for all your files and directories. Onestat requires a piece of
javascript be embedded into your page which sends off user data to
another server. This is a problem because: 1) your pages are bigger 2)
the readings don't work if the user has no javascript 3) It can't
analyze image requests or bad requests. 4) It requires the user to make
more connections to another server taking more time.
However, webalyzer requires a Perl enabled server as well as some more
web space.

--
| Brendan Gillatt |
| brendan {at} brendan \removethis// gillatt {dot} co {dot} uk |
| http://www.brendangillatt.co.uk |
| PGP Key: pgp.mit.edu:11371/pks/lookup?op=get&search=0x6E265E61|
Oct 9 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.