The HsService Class

  All services extend the HsService class. This is necessary in order to guarantee some common interface for all services. Since we are not as flexible about modeling our services as in IDL (the CORBA object definition language) we need to ensure some sort of base behavior that will allow us to dynamically load services. All services are implemented within the haystack.service package.

On instantiation, the HsService class will register its ServiceName (see Section )s with the name service. Furthermore, as we have stated above, HsService guarantees the existence of the init() and close() operations for loading and unloading. All services that need to provide some sort of startup and/or shutdown operations can overload these methods.