http://bugzilla.moblin.org/show_bug.cgi?id=8049
--- Comment #23 from yongsheng zhu <[email protected]> 2009-12-07 02:04:44 PST --- > > If the server name is empty, then return reports of all peers. This is > > easily > > known at the moment. However, for below inputs, what will be returned? > > "" --> all reports > > "" = "@default". > > So "" means all reports in the logdir specified in the @default context! No > other logdir is to be checked. If other contexts use the same logdir, then it > is okay to report sessions created in that other context (=> no need to match > sessions against the context in which they were created). so I'll add 'peer name' 'context info' in the LogDir and do these matches in > > "aServer" --> reports for 'aServer' > > "aser...@xxx" --> reports for 'aser...@xxx' > > "@default" --> ? > > "@specified" --> ? > > Same as "", with the logdir property taken from those contexts. ok. I see a declaration in the SyncConfig, * For example "scheduleworld" = * "ScheduleWorld" = * "schedulewo...@default", but not the same as * "schedulewo...@other_context" so 'aServer' and 'aser...@default' are the same. I'll follow up them. thanks Another issue is that is it ok to put these matches in the LogDir or in the SyncConfig? For the LogDir, it is in the charge of parsing and encoding dir names and doing the matches. However, for the sematics of peer and context, current the logic is described and written in it. > > 3) add second info in the dir name for accuracy. > > I don't understand this. Dir name is encoded in the 'peername-year-month-day-minute', I want to add a 'second' info. so it will be encoded in 'name-year-month-day-minute-second'. The root cause is that logs of different peers might be sorted together by their creation time. It is possible that two logs are generated within one minute. -- Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
