http://bugzilla.moblin.org/show_bug.cgi?id=5042
--- Comment #3 from yongsheng zhu <[email protected]> 2010-03-15 02:29:05 PST --- (In reply to comment #2) > (In reply to comment #1) > > If transferring all logs to clients, then it seems to me that this signal > > should be in DBusServer, however, i think session-specific output message is > > very useful because for commandline, we only want to know current session's > > logs instead of many others like client detach information. > > So logs of DBusServer is really useful to us? session-specific is enough for > > me. > > There's one problem with making it session specific: there is a race > condition. > If output is sent out via a new session directly after creating it, an > interested client might not have registered for signals in that new session > yet. It would miss the initial output. > > What about making the server a signal in the Server, but add a field which is > empty for general server output and the session when per-session? ACK. I'll add this signal in DBus Server level. -- Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
