Specification

The architecture of the xbook manager is shown in Figure 2.1. The servicing of a xbook request is decomposed into the following steps:

1. The xbook manager receives the forwarded request from the xbook server and dispatches it to an engine which can appropriately handle the request. In Figure 2.1, this is represented by a dispatcher entity.
2. The dispatcher looks up the xbook in its registry to find out its type.
3. The type of the xbook determines which xbook engine will handle the request.
4. The dispatcher passes the request to the appropriate xbook engine (in this case engine-1).
5. engine-1 locates the xbook in the xbook repository and handles the request.
6. The request results in the launch of an application.

Figure 2.1: xbook server architecture