Grouper Users - Open Discussion List

[Jeff McCullough <>]

Hi Chris,

Thanks for the info. We were just hooking our first real client app, and the 
paging thing is going to be a deal breaker for them. Putting part of the 
query in the request body is workable. The client app will be pulling group 
data that will frequently be in the 10s of thousands, and they would prefer 
to pull about 500 members at a time. Do you have a sense of how much effort 
adding paging to getMembers might be, and a rough time frame? I can maybe 
steer them to using LDAP groups, but the window of opportunity they have to 
change to using grouper for the app is fairly short. I'm a little worried 
they may be lost on other projects for a very long time. Okay… Enough 
pleading. :) Let me know.

Jeff



On Sep 13, 2012, at 10:07 AM, Chris Hyzer wrote:

> A couple of gaps unfortunately... for the params to be in the URL, it has 
> to be a Lite operation, and you can only get members from one group at a 
> time in a Lite getMembers or getMemberships operation.  If you want to pass 
> a JSON/XML/XHTML string in the body of the request, you can specify 
> multiple groups.  I don't see where there is paging on getMembers or 
> getMemberships... I think we need to add that.
> 
> https://bugs.internet2.edu/jira/browse/GRP-845
> 
> Thanks,
> Chris
> 
> 
> -----Original Message-----
> From: 
> 
>  
> [mailto:]
>  On Behalf Of Jeff McCullough
> Sent: Wednesday, September 12, 2012 6:48 PM
> To: 
> 
> Subject: [grouper-users] REST query string
> 
> Quick question. Is it possible to compose a REST like query in one URL that 
> uses paging and requests subjects from more than one group? 
> 
> Thanks,
> Jeff