Support code based configuration and consider removing deps on the crusty .NET config system about riak-dotnet-client HOT 2 CLOSED

My apologies for letting this slip under the radar! I didn't get a notification for this issue. Not sure why. I am sorry for not being on top of it.

Yes I did make a stance clear on HN about the initial structure and configuration design. One thing that I might not have been clear about was future plans.

Typical .NET teams are happy to have a bit of XML configuration lying around, and since this was a starting release we were aiming to hit the most common and accepted method. Adding the extra bit of functionality which lets you specify the configuration file in a different location so that it can be easily loaded in something like FSI. For initial releases this is more than enough and I don't think it's a blocker for people to get started with the library.

Having said all that we certainly aren't ignorant of the needs or suggestions of people like yourselves. JP and I have been talking about the configuration issues since we first released, along with the load-balancing code that we have in place.

Initially, the decision was made to put this code in place so that people didn't need to deploy a load balancer. This, so far, has been proved to be the right move given the feedback that we've had. Of the people who have so far actively used the library, only 1 or 2 have had stated that they're using a load balancer already. The rest are in the early stages of development and just have a Riak cluster that they're interacting with via a REPL/powershell/their app.

Only now are we starting to see more people say that they're looking to use a load balancer and hence won't need the functionality we have in CI.

There is definitely work we need to in this area. In the case where the user is dealing with a load balancer, the idea of having "nodes" and picking which one to use is pointless inside CI and just adds overhead. What we're aiming to do is have two different types of configuration, both which can occur via XML and through code using something fluent.

We have a RiakClusterConfiguration which will let you point to a cluster and have load balancing handled by CI, but I think we'll also add a RiakLoadBalancerConfiguration (or something with a better name) which lets you just point at a single load balancer and simply pools connections to the load balancer.

How does this sound?

Thanks very much for taking the time to write this issue up for us. JP and I really appreciate your interest and your feedback. It's something I'm going to be tackling in the coming days.

All the best!
OJ

from riak-dotnet-client.

For now the work that we planned to do with this has been done. In future if people are still unhappy they can open up another issue.

Cheers!

from riak-dotnet-client.