Understanding Data Connectors

[Cantor, Scott]

On 3/13/15, 12:20 PM, "Kanuch, Andrew" <Andy.Kanuch at sdstate.edu> wrote:
>
>But I left the second data connector in my attribute resolver XML file . One attribute definition (The one in the example) had the data connector as a dependency.  The attribute definition was not in any attribute-filters (which I realize in hindsight probably doesn't matter, and I should treat the Filter as just that.)

It does not matter, no. Filters cannot be used to reliably establish a set of attributes to resolve, so we don't do that. There are ways to limit it or configure it, but with the new ability in v3 to attach conditions to plugins, it's easier to always resolve everything and rely on conditions to disable things at the right times.

>What I am confused on is this: Was this triggered by the attribute definition, or the data connector? If I had left the data connector in, and simply removed the Attribute Definition that listed it as a dependency, would it still trigger the 15 seconds?

No, connectors only run as needed to supply attribute definitions with their source data.

-- Scott