Grouper Users - Open Discussion List

["Gettes, Michael" <>]

I think a lot of what you want to do could be achieved with messaging… all 
dependent on the message broker you choose, of course.

/mrg

> On Sep 10, 2018, at 1:59 PM, Black, Carey M. 
> <>
>  wrote:
> 
> All,
> 
> I expect the answer is "yes", but I have yet to identify the "sample code 
> that I am looking for". :)
> 
> In some cases, I can see a desire to defer the processing of a specific 
> event ( in the sequence of events) for a ChangeLogConsumer.
>       Is there a designed way to do that in the Grouper API?
>       Maybe a way to track the "number of times" the event was "deferrd"? ( 
> To avoid "stuck events" that "retry forever". )
> 
> In my case I can see some asyncronous dependeances that the 
> ChangeLogConsumer would need to "just wait" till the other thing is "done" 
> before it could continue with the event. 
> If I could "come back to the event" then I would not have to "block and 
> wait" on the event and hold up other events that could be processed that 
> are in the queue behind the "async depenedent" event.
> 
> 
> Part of me would even like to "force these events into a different stream" 
> so that they can be picked up by a different listner. ( Then that listner 
> would need to "send the event back" to the first listner too. )
> I may just be asking for to much from the built in ChangeLog/Messaging 
> stuff. ( But I hope not. )
> 
> 
> Anyone have a clue brick for me?
> 
> -- 
> Carey Matthew 
> 
> 
>