If we do things that way, all ClientAgents in a daemon would spawn the same client class.
It would preferable to allow the ClientAgent role configuration to specify which client to use (defaulting to what should actually be called "libastron" for a libastron client-side connection), so that each ClientAgent could be configured to spawn different client types.

For example, if someone had a game/application that ran on the web and through a mobile app, they may want to have a MobileClient and a WebClient, and differentiate on which client is spawned by which CA receives them (one CA would be listening for mobile connections, the other for web connections).