redundant connector configuration

[Matthias Lindner]

hello,

"the ndstonds-driver is built to communicate
with itself"

1) is it built to talk to more than one
instance of itself ?

2) is the ad-connector built to talk to
two remote loaders ?

and if it is/they are not, and i want to
set up two ndstonds- and ad-connectors:
3) will the loop detection work as well ?

could imagine that such a configuration was not
planned at all because all events get queued
and are synced upon come back of the
connectors -- including passwords.
4) but is this the case too for events on the
AD side ?

thank you a lot,
Matthias Lindner

[Matthias Lindner]

i guess it would be a case for scoping,
if two instances of a connector tried
to manage the same user.

umm..about the AD side..will passwords
sync if the DC with the remote loader
is temporarily down ??