</warning>
<section id="changelog">
<title>Changelog</title>
+
+ <section>
+ <title>7 September 2006</title>
+ <ul>
+ <li>KiSS modified the login procedure. It is now working again.</li>
+ <li>Generalized the startup scripts. They should now be insensitive to the specific libraries used. </li>
+ </ul>
+ </section>
+ <section>
+ <title>31 August 2006</title>
+ <ul>
+ <li>Added windows bat file for running the crawler under windows.
+ Very add-hoc, will be generalized. </li>
+ </ul>
+ </section>
+ <section>
+ <title>17 November 2006</title>
+ <ul>
+ <li>Corrected the packed distributions. The standalone distribution
+ had an error in the scripts and was missing libraries </li>
+
+ </ul>
+ <title>24 August 2006</title>
+ <ul>
+ <li>The crawler now uses desktop login for crawling. Also, it is much more efficient since
+ it no longer needs to crawl the individual programs. This is because the channel page
+ includes descriptions of programs in javascript popups which can be used by the crawler.
+ The result is a significant reduction of the load on the KiSS EPG site. Also, the delay
+ between requests has been increased to further reduce load on the KiSS EPG site. </li>
+ <li>
+ The crawler now crawls programs for tomorrow instead of for today.
+ </li>
+ <li>
+ The web based crawler is configured to run only between 7pm and 12pm. It used to run at
+ 5am.
+ </li>
+ </ul>
+ </section>
+
<section>
<title>13-20 August 2006</title>
<p>
</p>
<p>
The easy way to start is the
- <a href="installs/crawler/kiss/kiss-crawler-bin.zip">standalone program binary version</a>
- or using the <a href="installs/crawler/kissweb/wamblee-crawler-kissweb.war">web
+ <a href="installs/crawler/target/wamblee-crawler-0.2-SNAPSHOT-kissbin.zip">standalone program binary version</a>
+ or using the <a href="installs/crawler/kissweb/target/wamblee-crawler-kissweb.war">web
application</a>.
</p>
<p>
<title>General usage</title>
<p>
When the crawler runs, it
- retrieves the programs for today. As a result, it is advisable
+ retrieves the programs for tomorrow. As a result, it is advisable
to run the program at an early point of the day as a scheduled
task (e.g. cron on unix). For the web application this is
preconfigured at 5AM.
<note>
If you deploy the web application today, it will run automatically
on the next (!) day. This even holds if you deploy the application
- before 5AM in the morning.
+ before the normal scheduled time.
</note>
<p>