Can we maybe add another construction with the original signature that creates and populates the Config object and then calls this constructor?  Seems like an easy way to keep the API compatible, or do you think we don't care because this will go in 2.0?