Tickets :: [#2626] New parameter for LDAP driver

6.0.0-beta1

11/9/25

Summary	New parameter for LDAP driver
Queue	Turba
Queue Version	HEAD
Type	Enhancement
State	Resolved
Priority	1. Low
Owners
Requester	tevans (at) tachometry (dot) com
Created	09/19/2005 (7356 days ago)
Due
Updated	09/21/2005 (7354 days ago)
Assigned
Resolved	09/21/2005 (7354 days ago)
Milestone
Patch	No

09/21/2005 06:31:08 PM	Chuck Hagenbuch	Comment #4 State ⇒ Resolved	Reply to this comment
Committed, thanks. The patch to sources.php.dist was wonky and didn't apply cleanly, so please check it to make sure I got it right. In the future please use cvs diff -uRN to generate a single diff for multi-file patches.

09/20/2005 08:24:42 PM	tevans (at) tachometry (dot) com	Comment #3 New Attachment: turba_param_patch[1].txt	Reply to this comment
OK - I added a bit of information to the sources.php.dist file to explain the new parameter and provided an example usage. This attachment includes both the original patch and the added docs.

09/19/2005 04:32:06 PM	Chuck Hagenbuch	Comment #2 State ⇒ Feedback	Reply to this comment
This makes sense to me, but can you add documentation on the new option and changed behavior to the examples and parameter listings in sources.php.dist?

09/19/2005 09:22:56 AM	tevans (at) tachometry (dot) com	Comment #1 State ⇒ New Priority ⇒ 1. Low Type ⇒ Enhancement Summary ⇒ New parameter for LDAP driver Queue ⇒ Turba New Attachment: turba_param_patch.txt	Reply to this comment
I ran into some difficulty using the 'checkrequired' and 'checkrequired_string' parameters for the LDAP driver because these parameters also triggered a heavyweight syntax check (field by field via isPostalAddress method) that spiked the CPU on both the web server and the LDAP server. I propose using an alternate parameter name ('checksyntax') to isolate these two features from each other. This patch allowed me to use the auto-fill functionality for newly added entires via the 'checkrequired' parameters with no appreciable performance penalty.