Combining Information from Multiple Internet Sources

module. At the end of this section the sequence diagram which depicts the information contained in
this section is presented.
As the first step of the process the user provides the query and the algorithm name as HTTP
request parameters. Those are read and checked by the GatewayServlet object which displays a
message if the parameters are invalid. Then the GatewayServlet wraps the parameters into a
SearchParams object, sets those as an HTTPSession attribute and forwards session object to the
SearcherClientAgent. The SearcherClientAgent then creates a new Manager Agent (MA) with a
random name and stores its AID as a session attribute. Then it forwards the created SearchParams
object to the Main module entry point - the newly created MA- and waits for the response from the
agent. Afterwards, the MA receives SearchParams which is in turn unwrapped providing the query
and the algorithm. Then search engines are queried and algorithm finishes processing the List of
results is returned to the SearcherClientAgent. Depending on the case if the algorithm was able to
yield the answer or not, the resulting webpage will contain buttons to provide feedback for specific
URL. If the webpage contains no buttons for feedback, the process is finished. If, however, the
webpage contains buttons for providing feedback, the user may view web pages under those URL
and then provide feedback by clicking the button next to the URL he chooses as the best. Then the
URL is forwarded to the GatewayServlet object as HTTP request parameters. The first parameter
contains the link name and the second contains the actual URL. Those parameters are then wrapped
into the HTMLTagA object, set as a session attribute and forwarded to the FeedbackAgent.
FeedbackAgent forwards the HTMLTagA object to the Main module (MA) which can finish its
processing tasks. After finishing processing tasks MA is still alive waiting for another request.
However when the server session has ended the MA is destroyed immediately.
The following sequence diagram depicts the information described in the above part. This
diagram can be viewed as a summary of what was described before as it presents the workflow and
information flow between components of this module.
9