One other thing to consider is that the implementation of `configure-web-server` today -- which is called by `create-webserver` -- does both the validation of content from the config as well as the construction of the options map used in `create-server`.  If all of the options map population is moved over to the `start` phase -- including the validation logic -- any of the current code which would throw an Exception due to bad content found from the config would result in the tk webserver JVM process remaining in a "hung" state -- like with the `java.net.BindAddress` conflict issue discussed previously.  As a best practice, would it make sense to separate any initial settings validation to being done in the context of `init` or allow it to be done during `start` or later as well but with the burden of wrapping all of the functionality in a `shutdown-on-error`?  Maybe wrapping all of your logic in `start` in a `shutdown-on-error` makes sense to do all of the time?