SiteWatch Technology:
SiteWatch is using LinkSearch core technology which is a restrained robot spider.
SiteWatch is multithread and each thread is one robot spider downloading, searching and processing
the content of one link. When a thread finds a link, a new thread is created to process the new link.
Generally download time for a page is much longer than processing the content of a page.
Since threads run simultaneously download time is reduced to a fraction of a single thread processing.
Future Plans: Improvements and enhancements.

User Friendly:
SiteWatch is an easy to install and operate application.
It is downloaded through the Internet in a zip format.
The file size is around 40 k. The zip file needs to be unzipped to any directory and SiteWatch is ready
to start.
Once the required initial information regarding the target web site and email is provided through a
user friendly GUI, SiteWatch will continue its operation permanently without a need to configure it
ever again, unless the information provided has changed.

Purpose:
Internet and Intranet is dynamic in nature  and as web sites grow in size, managing and maintaining
them requires sophisticated tools to monitor the links.
SiteWatch is designed to respond to this particular need to free web masters from the tedious task of
constant review of their sites.
Java(TM)  language was selected to provide a uniform behavior on all platforms

Performance:
SiteWatch is optimized for high speed and  requires a good chunk of memory. There is no
answer to how much memory.  since SiteWatch is a multithreaded software, its memory requirement
depends on the number of the links per page and the number of pages per site and the speed of the modem or
network. It could be processing 1000 or more files at any time.
To overcome this obstacle a provision has been provided to limit the number of active threads.
The general rule is, start from few threads and run the SiteWatch, and on each run progressively
increase the number of threads to determine the optimum number of threads.  if the machine does not
have enough memory, Java(TM)  Runtime Environment will send some message and the application will
and then stop.
Due to some Intranet issues, SiteWatch will not operate within the confine of an Intranet and requires
access to WWW. Presently there is an ongoing work to resolve these issues.