version 1.10, 2004/01/14 21:40:51
|
version 1.13, 2004/01/16 11:21:14
|
Line 150 Currently indexing is not implemented on
|
Line 150 Currently indexing is not implemented on
|
\item construct remote (141.14.236.86) index for each file at |
\item construct remote (141.14.236.86) index for each file at |
per-change or daily intervals |
per-change or daily intervals |
\item store indices locally in |
\item store indices locally in |
|
archimedes/data/db/PROJECT_NAME/CORPUS_NAME/WORK |
|
\item 2 progs on server 1. cgi: indexer 2. backend da_remote |
|
\item 2 progs on client 1. cgi: sendindex 2. backend getindex |
|
\item indexing transaction handled by two cgi scripts, one on the |
|
server the other on the client [this is the 1st implementation bcs |
|
its easiest and there are no port issues, but probably it'd be |
|
better to have a separate port]. |
|
\item client cgi: getindex -- sends 1. list of files to index |
|
2. uri to which xml notification of completion is to be sent. Upon |
|
notification, activates backend prog that fetches and installs the |
|
indices. |
|
\item server cgi: indexer receives filelist and notification |
|
addess. Activates backend that fetches files, indexes, places |
|
completed indexes in a networked location, then sends xml |
|
notification back to client. |
|
\item single script provides backend access to indices |
|
\item leave front-end issues like display, collection and navigation |
|
to web-design programmers. Do only a sample for now. |
\end{enumeration} |
\end{enumeration} |
|
|
\subsubsection{Morphology} |
\subsubsection{Morphology} |