Grouper Developers Forum

[Shilen Patel <>]

On 10/27/11 1:19 PM, "Jim Fox" 
<>
 wrote:

>
>In general I prefer improvements that help rather than hinder
>performance.
>
>It seems to me wasteful and unnecessarily complex to build a new
>subject source inside grouper that mostly duplicates an already
>workable subject source mechanism.  An automated process presents
>some credential, let's say an x509 certificate.  An off-the-shelf
>jdbc subject source easily manages subjects that have the CNs of
>the certificates as names, or ids, or whatever.  It requires nothing
>new except a means to update the database of automated clients---not
>a difficult task.
>
>My second comment is that this capability, even if I don't use
>it, will slow down grouper.  For example, changing the name of
>a stem will require a search for downstream subjectIdentifiers.
>This might be a small, even trivial concern, but let me remind
>you of the published comparison of performance between grouper
>1.6 and 2.0.  As I recall 2.0 is 'only' 15-20% slower than 1.6.
>A couple more upgrades like that and it won't run at all.


If you don't use this capability, performance shouldn't be any slower if
you rename a stem.  The current code already goes through child groups
since it has to rename the groups, so we already know if each child group
is a plain group, role, or entity.  And the search for the
subjectIdentifier won't happen if it's not an entity.

Thanks!

-- Shilen


>