Changeset 6343


Ignore:
Timestamp:
2004-01-05T17:22:45+13:00 (20 years ago)
Author:
kjdon
Message:

small changes

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/gsdl3/docs/manual/manual.tex

    r6335 r6343  
    568568\label{tab:gsf-select-types}
    569569\begin{tabular}{ll}
     570\hline
    570571\bf Select Type & \bf Description\\
     572\hline
    571573current & The current section \\
    572574parent & The immediate parent section\\
    … …  
    576578children & The immediate children sections of the current section\\
    577579descendents & All the descendent sections\\
     580\hline
    578581\end{tabular}
    579582\end{table}
    … …  
    727730accessing the javadoc\\
    728731
     732\subsection{Overview of modules??}
     733
    729734A Greenstone3 'library' system consists of many components: MessageRouter, Receptionist, Actions, Collections, ServiceRacks etc.  Figure~\ref{fig:local} shows how they fit together in a stand-alone system.
    730735
    … …  
    742747Functionally Collection and ServiceCluster are very similar, but conceptually, and to the user, they are quite different.
    743748
    744 {\em ServiceRack}: these provide one or more services - they are grouped into a single class purely for code reuse, or to avoid instantiating the same objects several times. For example, MGPP searching services all need to have the index loaded into memory. Services provide the core functionality for the system, e.g. searching, retrieving documents, building collections etc.
     749{\em Service}: these provide the core functionality of the system e.g. searching, retrieving documents, building collections etc. One or more may be grouped into a single class (ServiceRack) for code reuse, or to avoid instantiating the same objects several times. For example, MGPP searching services all need to have the index loaded into memory. Services provide the core functionality for the system, e.g. searching, retrieving documents, building collections etc.
    745750
    746751{\em Communicator/Server}: these facilitate communication between remote modules. For example, if you want MR1 to talk to MR2, you need a Communicator-Server pair. The Server sits on top of MR2, and MR1 talks to the Communicator. Each communication type needs a new pair. So far we have only been using SOAP, so we have a SOAPCommunicator and a SOAPServer.
    … …  
    10701075</response>
    10711076\end{verbatim}\end{gsc}\end{quote}
    1072     <field shortname="ZZ" name="allfields" />
    1073     <field shortname="TX" name="text" />
    1074     <field shortname="TI" name="Title" />
    1075     <field shortname="SU" name="Subject" />
    1076     <field shortname="ORG" name="Organization" />
    1077     <field shortname="SO" name="Source" />
    10781077
    10791078\begin{figure}[t]
Note: See TracChangeset for help on using the changeset viewer.