Coil

Twisted applications should be easily configurable by system administrators. For example, a system administrator should be able to deploy a chat server and configure it to use kerberos for authentication.

The user interface for this configuration should be uniform across all Twisted applications. It should be provided by framework code sitting "in front of" application code: the user interface code allows objects to be selected, then those objects are passed to application code, so that the application code isn't even required to be aware of the configuration system.

This requires a mechanism for describing what kinds of objects are required for an application. It also requires a mechanism for defining what objects of various kinds are available on a system (enumerating and instantiating them).