[Tickets #7478] Re: adding contact to chained ldap slave server causes error message

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7478
------------------------------------------------------------------------------
  Ticket             | 7478
  Updated By         | robb at wtg.cw.com
  Summary            | adding contact to chained ldap slave server causes
                     | error message
  Queue              | Turba
  Version            | 2.3
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


robb at wtg.cw.com (2008-10-24 05:54) wrote:

> I'm not happy about adding a delay for all backends that in most
> cases will just slow users down pointlessly. I could see getting rid
> of the read, I guess, but then you're likely to get this error when
> redirecting to the new contact.
>
> I don't know enough about LDAP to know how common this is and how
> much it's worth compromising everyone else's experience because of it.

Sure, I can see that.

How about searching immediately, then try again one second later if  
you fail, with one further retry. That should avoid a delay for those  
that don't need it, but allow some leeway for those that do.

Probably not hugely common setup, but hopefully this suggestion can  
avoid that.