----- Original Message -----
From: "Susan" <>
Newsgroups: microsoft.public.word.web.authoring
Sent: Wednesday, June 02, 2004 6:59 PM
Subject: Re: View Source

Hello Susan,
                      Your not required to learn Java, which is a form of
scripting in order to use it successively. A good and easy example of Java
implementation is in visitor stats.
Ex: http://sitemeter.com/
You insert a few lines of code within each page and are provided with stats.

The only way of getting around a user having Java turned off is NOT to use
Java :-((

Does your web host offer "visitor logs?"
Many hosts offer stats created from logs, however in most instances these
stats are useless because they are snipped off in their completeness, as the
host desires because he's prvoviding stats for the mass of his customers.

With visitor logs, you have the capability of seeing a more in-depth
picture of what you visitors are doing as well as using the information
conained in the logs to limit their activity.
You limit their activity with "server side" capabilities.

One of which I previously offered, requires three tools.
( http://www.webmasterworld.com/forum13/1183.htm?highlight=bot+trap )

Most intruder/hackers are not doing so by hand (so-to-speak) rather, they
are using a software to make their work easier and more productive.
1) You create a tranparent image, which the intruders software hits and
providing activiation of
   your server side perl script.
2) Perl
3) The Perl script records the visitors IP address and immediately denies
that intruders IP range      any further activity by making a change into
your htaccess file. Some of the users of this
    specific Perl script have even added notification to the webmaster of
the intrusion.

You should note that just because your server side tools provide you with an
IP address, that doesn't necessarily mean that the IP address is correct.
Nor will the IP range tell you anything except a number. That number will
NOT tell you it's John Doe from your competitors neighboring field office.

IMO and given your currrent knowledge the fact that you drew  the "shortest
straw," the simpliest solution for you and all involved to research research
the capabilities and/or limitations of your "password-restricted site" and
IF neccessary find a more secure alternative.

Analyzing Daily LOGS is the easiest solution to visitor activity. If there
are only a small group of you, I cannot imagine the log lines realted to
your portion of your companies website would be that extensive. Your
webmaster could create "very" quickly a server side script which would send
you the daily, the specific log traffic lines.
From those lines, you could progress slowly at understanding this scenario
Vs., taking on a large project all at once.

If you need further assitance on this?
I'll be gald to provide some extenive links which will assit you.
Please mail me off-line this topic if HIGHLY off-topic in this NG.

info at mi dash harness dot com