Grouper Users - Open Discussion List

[David Langenberg <>]

We have not seen any updates with respect to Google's API limits.  If your 
throttle is working for you, then I wouldn't mess with it, otherwise, their 
recommendation is to implement exponential back off.

https://developers.google.com/google-apps/provisioning/limits

Dave

--
David Langenberg
Identity & Access Management
The University of Chicago




On Mar 12, 2013, at 1:42 PM, Steven Carmody 
<>
 wrote:

> Hi,
> 
> We'll be making some changes to the mechanisms we use to replicate groups 
> from MACE Grouper to Google. We currently have the Grouper Change Log 
> process send a message on a Message Bus; various listeners pick up the msg 
> and replicate the change into various external directories and services.
> 
> One of those listeners talks to google. Traditionally, one of the problems 
> with this mechanisms has been that google "throttles" the total volume of 
> thruput thru its interfaces. The Listener used a weird adaptive algorithm 
> to keep the traffic volume just below google's trigger point.
> 
> Since we're about to make some changes here, I thought it would be a good 
> time to ask whether anyone knows whether google's throttling algorithm has 
> seen any significant changes in the last year or so. Have the parameters on 
> the google end changed enough that we should change our "self-throttling" 
> algorithm ?
> 
> Thanks for any hints and information!