> When I do a bind to the consumer(slave) I also see a bind to the
> provider(master) this seems really silly. My understanding is that
> this behaviour is caused by needing to centrally store login attempts.
> I have raised this matter previously but just wanted to double check
> that the behaviour I am seeing is expected and not due to a
> misconfiguration on our part.
Are you using Chain On Update for Binds?
We are indeed, we used that howto to set it up. Reading it now again it does say it will
use the chaining backend for binds. Why is that? If we replicate changes down to the
consumer how can the data be "fresher" than the consumer?
In order to protect our email recipients, Betfair Group use SkyScan from
MessageLabs to scan all Incoming and Outgoing mail for viruses.