written-up caveats on g_main_context_iteration?

[Rick Jones <rick jones2 hp com>]

I have a few places in netperf4 where a thread executing code (I'm 
eliminating threads in the controller side) will loop looking for a 
given test (or tests) to enter a specific state.  Going event-driven I 
_might_ be able to code-up some FSM-like thing for this bit, but was 
wondering if I might be able to use g_main_context_iteration instead to 
allow the code that wants to "wait" to let the loop run to let the test 
state to be updated etc etc.

Are there any non-trivial caveats in using g_main_context_iteration?

rick jones

tell tests to enter init
wait for tests to enter init
tell tests to enter load
wait for tests to enter load
tell tests to enter measure
wait for tests to enter measure

that sort of thing