Work on Config Service 3.0 is going to start in a few weeks. I am going to look at MSE capabilities, and make a determination on what can/should be rolled in. I do want to roll in a router-based service; ala MSE; and will likely look to leveredge that code. Other plans:
-A client-light implementation that would allow clients to take advantage of load balancing/failover without implementing config service itself (backend services would implement the config service; but node information would be dynamically retrieved directly from the backend services) -Optional ability to store binding configuration information in the repository (vs. having to use config files); and dynamically update this info/upload new bindings via ConfigWeb -A new layout/UI for configweb, tested on IE7, IE8 and Firefox -Updates for Win7 -Updates for .NET CLR4, VSDev10(both still in beta right now) -Dublin integration where it makes sense -Other ideas? Now is the time to offer up suggestions.
Timing would be several months away still.
-Greg Greg Leake, Microsoft |