Question about FailOverDataConnector

[Rod Widdowson]

> I include it in exportAttributes for both the primary and fail over, like I said, it resolves attributes for both.

I'd need to look more closely but this will be because the resolver says "I need this attribute, here are all the ways of getting
it, I'll resolve them all".   After all a priori it doesn't know if that the failover connector is only being used as a failover -
it could be being used in multiple places.

Of course it is slightly weird that the attribute gets resolved via the exportAttributes  on another data connector.  

> If it works, then it probably is implemented from within the connector that "failed", so it has a chance to honor its own
exportAttributes rule.

Exactly.

I think for the ease of other people reading the configuration I would end up with an old style attribute definition with an
explicit dependency.  Although you are in fact saying the same thing, it is more obvious to explicitly state that:

AttributeDef 'A' depends on Data Connector 'D' to get the input.   If DataConnector 'D' cannot do the right thing then it will ask
its friend connector 'F' to do the work and then DataConnector 'D' will complete the resolution process and pass things back to 'A'.