nope that is it. The method I added, and would still like to get buy in, is to add backgroundProcess() as a method to the manager interface. That way, any manager can take advantage of the background thread from the context calling that method. If we don't want to change the interface, we can either add in reflection which I'm not a big fan of since I think managers should know what is going on, or skip the backgroundProcess for custom managers, I'll just implement a thread in the cluster instead.
what do you think?
I think I'm +0 on adding this.
Rémy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
