(in the trunk, not the stable release, as of today)
Due to popular demand, there are a couple of enhancements to the parametric
("new") router.
One is the ability to specify a default function per controller. In the
configuration, default_function has been (and can still be) a string, which
specifies a default function for all controllers in an app. default_function
can now be a dictionary, where the keys are controller names.
In support of this functionality, the variable 'functions', which has been a
list of strings (function names in the default controller) can now be a
dictionary of such lists, keyed by controller name.
If you use these formats, be sure to provide an entry for each controller;
results for a controller not included are not defined by the current
implementation.
The other change is also function-related. It's been possible to map a domain
name (with optional port) to an app, or to an app/controller. You can now also
map a domain to an app/controller/function. The use case that inspired this
capability was the use of a subdomain dedicated to a particular administrative
function; a bit unusual, but since the a/c/f syntax was a natural extension of
the current logic, I extended it.
The features have been tested with unit tests, but have had little or no
real-world exposure, so feedback will be appreciated.
