Another thought that this has kicked off. If we have policy models that are potentially not specific to a particular binding or implementations type, e.g. http/ssl (because quite a few bindings use HTTP under the covers), then that gives us a bit of a problem with the provider model as that's keyed on the model type rather than the model type and the technology it's being applied to.
The easy way round this is to specialize the models for each binding (technology) that uses them then we get a binding specific model. Seems a bit of a shame though as the policy set will end up being applied to a particular technology anyhow and this could form part of the key when choosing the provider. Not sure that we have enough generic policy model/technology specific policy providers that this is a big deal but just throwing it out there. I'll give it some though as I add more features to the ws binding. Simon
