@@ -46,15 +46,15 @@ <h3>datamodel</h3>
4646 such essentials as the CandidateURI and CrawlURI classes that wrap the
4747 discovered URIs for processing.
4848
49- < h3 > admin </ h3 >
49+ < h3 > restlet </ h3 >
5050 < p >
51- {@link org.archive.crawler.admin org.archive.crawler.admin }
51+ {@link org.archive.crawler.restlet org.archive.crawler.restlet }
5252 < p >
53- The < tt > admin </ tt > package contains classes that are used by the Web UI.
54- This includes some core classes and a specific implementation of the
55- < tt > Statistics Tracking </ tt > interface found in the < tt > framework </ tt >
56- package that is designed to provide the UI with information about
57- ongoing crawls.
53+ The < tt > restlet </ tt > package implements the Web UI and REST API. Its
54+ resources provide access to the crawl engine, jobs, configuration,
55+ scripts, and reports. The
56+ {@link org.archive.crawler.reporting.StatisticsTracker StatisticsTracker}
57+ supplies progress information and reports for ongoing crawls.
5858
5959 < h2 > Pluggable modules</ h2 >
6060 < p >
@@ -96,7 +96,7 @@ <h3>Processor</h3>
9696 < li > Post-processing chain
9797 </ ol >
9898 Each of these chains contain any number of < tt > processors</ tt > . The processors
99- all inherit from a generic {@link org.archive.crawler.framework .Processor
99+ all inherit from a generic {@link org.archive.modules .Processor
100100 Processor}. While the processors are divided into the five categories above that
101101 is strictly a high level configuration and any processor can be in any chain
102102 (although doing link extraction before fetching a document is clearly of no
@@ -105,12 +105,12 @@ <h3>Processor</h3>
105105 Numerous processors are provided with Heritrix in the following packages:< br >
106106 {@link org.archive.crawler.prefetch org.archive.crawler.prefetch} package
107107 contains processors run before the URI is fetched from the Internet.< br >
108- {@link org.archive.crawler .fetcher org.archive.crawler .fetcher} package
108+ {@link org.archive.modules .fetcher org.archive.modules .fetcher} package
109109 contains processors that fetch URI from the Internet. Typically each
110110 processor handles a different protocol.< br >
111- {@link org.archive.crawler .extractor org.archive.crawler .extractor} package
111+ {@link org.archive.modules .extractor org.archive.modules .extractor} package
112112 contains processors that perform link extractions on various document types.< br >
113- {@link org.archive.crawler .writer org.archive.crawler .writer} package contains
113+ {@link org.archive.modules .writer org.archive.modules .writer} package contains
114114 a processor that writes an ARC file with the fetched document.< br >
115115 {@link org.archive.crawler.postprocessor org.archive.crawler.postprocessor}
116116 package contain processors that do wrapup on the processing, reporting links
@@ -131,10 +131,10 @@ <h3>Scope</h3>
131131 of a crawl can be more easily achived using one of the existing scopes and
132132 modifying it with appropriate filters.
133133 < p >
134- {@link org.archive.crawler.framework.CrawlScope CrawlScope} - Base class for
135- scopes. < br >
136- {@link org.archive.crawler.scope org.archive.crawler.scope} package. Contains
137- provided scopes .
134+ {@link org.archive.modules.deciderules.DecideRule DecideRule} is the base
135+ class for rules used to define scope. The
136+ {@link org.archive.modules.deciderules org.archive.modules.deciderules}
137+ package contains the provided rules .
138138
139139 < h3 > Statistics Tracking</ h3 >
140140 < p >
@@ -143,16 +143,12 @@ <h3>Statistics Tracking</h3>
143143 < p >
144144 These modules can both interrogate the < tt > Frontier</ tt > for what sparse
145145 date it exposes but they can also subscribe to
146- {@link org.archive.crawler.event.CrawlURIDispositionListener Crawled URI
146+ {@link org.archive.crawler.event.CrawlURIDispositionEvent Crawled URI
147147 Disposition} events to monitor the completion of each URI that is processed.
148148 < p >
149- An interface for {@link org.archive.crawler.framework.StatisticsTracking
150- statistics tracking} is provided as well as a partial implementation
151- ({@link org.archive.crawler.framework.AbstractTracker AbstractTracker})
152- that does much of the work common to most statistics tracking modules.
153- < p >
154- Furthermore the < tt > admin</ tt > package implements a statistics tracking
155- module ({@link org.archive.crawler.admin.StatisticsTracker StatisticsTracker})
149+ The {@link org.archive.crawler.reporting org.archive.crawler.reporting}
150+ package provides a statistics tracking module
151+ ({@link org.archive.crawler.reporting.StatisticsTracker StatisticsTracker})
156152 that generates a log of the crawlers progress as well as providing information
157153 that the UI uses. It also compiles end-of-crawl reports that contain all of the
158154 information it has gathered in the course of the crawl.< br >
0 commit comments