The objects that represent configured transports and message handlers are loaded into the Agent at startup based on the configuration file <servicecontextname>_objects.xml on the server side, and the optional client-objects.xml on the client side. It is this mechanism that makes all configured transports and message handlers available at runtime for dynamic switching. While this mechanism is set up for you automatically by the HydraExpress code generator for the services you create, it is also a generalized mechanism that you can exploit. For example, you could load an object representing a database connection, and your service application could use this object to obtain access to the database. For more information about named objects, see Chapter 16, Named Objects.