On 08/07/2013 07:25 PM, Xuelei Fan wrote:
Maybe just as Sean said, the SPI mode is introduced later, and we need to consider compatibility issue. As in this update, we are trying to update the default implementation, it should be a chance to update the implementation to follow the model of SPI. It should be safe as the update only impact implementations.
Yes, I believe it is because of compatibility issues since ConfigurationSpi was added in a later release. Also see the Configuration.ConfigDelegate class.
Anyway, I'm going to push this since it isn't specifically relevant to this bug. If you think there's some additional improvement that can be done, please file a separate RFE.
Thanks, Sean
