Grouper Developers Forum

[Tom Zeller <>]

I was thinking there would be one thread per provisioned target. The
optimization here is that grouper would only have to be queried once
for source data (the attribute resolver), and then these attributes
would be passed to each target.

Perhaps I should assume single-threadedness for now, make sure the
code we write is thread safe, and consider multi-threadedness later.

On Tue, Jan 26, 2010 at 10:25 AM, Chris Hyzer 
<>
 wrote:
> We could synchronize the access to the spml library on the same object.
> Or do we need it to be more efficient where we need multiple threads doing 
> things at the same time? (i.e. even with WS having an operation which says 
> 'provision now, something changed', we could set a timer so that it doesn't 
> necessarily provision, but waits 5 seconds, then provisions, and in the 
> meantime, if more 'provision now' requests arrive, they are ignored)
>
> Thanks,
> Chris
>
> -----Original Message-----
> From: 
> 
>  
> [mailto:]
>  On Behalf Of Tom Zeller
> Sent: Tuesday, January 26, 2010 10:49 AM
> To: Grouper Dev
> Subject: [grouper-dev] ldappc-ng and openspml thread safety
>
> The openspml library currently used by ldappc-ng is not always thread
> safe (https://openspml.dev.java.net/issues/show_bug.cgi?id=5). It's
> good that there is now some sort of development process underway for
> openspml.
>
> If, one day, we expose provisioning via grouper-ws, I assume thread
> safety is an issue. Besides finding another spml implementation, is
> there a way to configure tomcat or code grouper-ws to workaround
> thread safety issues ?
>
> TomZ
>