(In reply to comment #25) > > I'd prefer to not depend on Synthesis progress events for this. We don't have > > those in the server engine. Instead just set the processing/waiting according > > to the state changes in SyncContext::doSync(). We know when our transport agent > > is busy. > > Yes, Synthesis server don't generate progress events. so it depends on stepCmd > in the doSync(). > I want to add a new virtual function 'void reportStepCmd(sysync::uInt16 > stepCmd)' in the SyncContext. It is called in the loop at the end of each step > command . Session in dbus server receives this stepCmd info and set its status. That sounds reasonable.