Subject: Grouper Users - Open Discussion List
Re: [grouper-users] UI, Pagination and the Subject interface
- From: Tom Barton <>
- To: Chad La Joie <>
- Subject: Re: [grouper-users] UI, Pagination and the Subject interface
- Date: Fri, 21 Jan 2005 09:48:43 -0600
Chad La Joie wrote:
Here are some more naive questions as I try to come up to speed on
The data source which you are pulling group information from can be
configured correct? Meaning University A could store their groups in
an LDAP while University B could store their groups in an relational
The Groups Registry backing the Grouper API is necessarily relational. Sites might load group related info into the Registry or provision it from there to stores of whatever sort.
If that's the case a pagination API would need to be>
abstracted from any particular data source.
Assuming people are subjects, are groups subjects too, or are groups
some other data object which contain subjects?
Grouper 0.5 ships with 2 subjectTypes: 'person' and 'group'. Sites can extend the set of subjectTypes. The subject interface is an abstraction for dealing with subjects of different subjectTypes. For each subjectType a declared adapterClass implements the interface, allowing sites to provide site-specific resolution services for 'person' and other subjectTypes. The Grouper API includes an adapterClass for the 'group' subjectType, and for its sake pagination will be tied to the relational backend somehow.
- Re: [grouper-users] UI, Pagination and the Subject interface, Chad La Joie, 01/21/2005
- Re: [grouper-users] UI, Pagination and the Subject interface, Tom Barton, 01/21/2005
Archive powered by MHonArc 2.6.16.