Grouper Developers Forum

["GW Brown, Information Systems and Computing" <>]

The custom source adapter depends on local infrastructure, and so would not 
be directly applicable elsewhere. The general approach to caching and 
preloading may be abstractable such that sites would only have to extend a 
class and implement methods to retrieve all their subjects - we could 
possibly define an optional interface for this.

We don't have a last modified field on our bundled subject table so there 
we would have to reload everything. The JNDI adapter might fall foul of 
configured LDAP retrieval limits. For sites which never delete an identity 
I guess there may just be too many identities, however, preloading just 
enough attributes to support search results and membership listings and 
using lazy loading of other attributes  - for Subject Summary type pages - 
may work.

I'll give it some further thought and see if I can come up with something.

Gary





--On 16 January 2008 15:05 -0600 Tom Barton 
<>
 wrote:

>  wrote:
> > I have added some comments to the Wiki  -
> > <https://wiki.internet2.edu/confluence/display/GrouperWG/UI+Analysis>
>
> You said "At Bristol I am working around this issue by pre-loading and
> caching all my Subjects (I use a custom Source adapter)." Any chance you
> can share that source adapter with us? Maybe as a contrib?
>
> Tom



----------------------
GW Brown, Information Systems and Computing