Phil Dibowitz wrote: > Stephen Warren wrote: >> As you may have noticed, congruity does this already at the application >> level. This whole process obviously takes some time, and could even fail >> (e.g. if user unplugs the remote.) This change probably requires >> reset_remote having a callback to indicate progress... > > reset_remote has no way of knowing progress, it sends a command and the > remote disappears. > > I did a deinit_concord and then have a loop while we wait for it for a > certain amount of time. If it doesn't come back, we report it as an error.
Oops. For some reason, I assumed you'd made libconcord do the wait-for-reboot loop internally. Now that I actually read the code, I see concordance.c does this, which makes much more sense! ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
