Strategies for multiple gconf notifications

If I have an intensive process that should be rerun in response to any
one of twenty configuration keys, how might I prevent my application
from re-running that process 20 times instead of just once, when
changing all the keys at one time.

I guess I could just append each notification key to a GList, and use a
g_timeout handler to notify my application about batches of changes, if
anything changed, at regular intervals.

Or is there some existing API or known strategy to deal with this
situation?

I've tried temporarily setting a "disabled" key but querying this
generally returns true well before the notifications have arrived.

-- 
Murray Cumming
[email protected]
www.murrayc.com
www.openismus.com