Subject: Grouper Developers Forum
- From: "blair christensen." <>
- To: "" <>
- Subject: Re: [grouper-dev] some results with ldappc
- Date: Fri, 20 Jul 2007 10:39:37 -0500
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=QMZ3YqZpII6FbnobyiGTBrtk7iuren865fJLZwCbR/kTIb6xxWX8RaXH/JmVDBSr//tlj410/xNowJFCNlcJE4Dr7QZOqaLpiZVcDSE2LvuwpMe3Odfn2bIXUq6FVj1k1UEeK+e8L3SE2sAIG9luqxaBGoCNpHZoN/3IN5+vXNk=
However, my sense is that the algorithm that ldappc uses to maintain
the membership of these groups -- when a run includes a number of
membership changes -- may be less than optimal....
I haven't looked into that part of the Ldappc code yet, or really any
part that touches LDAP, but I have spotted some areas where between
some tweaks to Ldappc and the Grouper API we *should* be able to
improve its performance when interacting with the Grouper API fairly
significantly. I think I'll be able to start working on those code
changes next week.
- Re: [grouper-dev] some results with ldappc, blair christensen., 07/20/2007
Archive powered by MHonArc 2.6.16.