>From a security point of view we have adapted a master-slave relationship where writes are performed at the master level server and reads are performed via the slaves via port 389.
Data is replicated from master - to - slave via slurpd. "Zumwalt, Robert" <[EMAIL PROTECTED]> 11/03/2008 10:42 a.m. To <perl-ldap@perl.org> cc Subject RE: ports I don't think it is the norm... in our production environment we have 12 cache servers which are optimized for searches and respond to one port.. and a single separate server which is optimized for write requests. Robert -----Original Message----- From: Quanah Gibson-Mount [mailto:[EMAIL PROTECTED] Sent: Monday, March 10, 2008 3:03 PM To: Zumwalt, Robert; perl-ldap@perl.org Subject: Re: ports --On Monday, March 10, 2008 2:58 PM -0500 "Zumwalt, Robert" <[EMAIL PROTECTED]> wrote: > Is there a way to designate a separate read port from write port? Or do > I need to create 2 separate connections if I want to perform this type > of action? AFAIK, there is no such distinction at all in LDAP... You could create two separate *connections* and have one do write, and one do reads... --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration E-MAIL CONFIDENTIALITY NOTICE: The contents of this e-mail message and any attachments are intended solely for the addressee(s) and may contain confidential and/or legally privileged information. If you are not the intended recipient of this message or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and any attachments. If you are not the intended recipient, you are notified that any use, dissemination, distribution, copying, or storage of this message or any attachment is strictly prohibited.
