http://bugzilla.moblin.org/show_bug.cgi?id=7838
Chen Congwu <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|SyncEvolution |*Feature Request AssignedTo|[email protected] |[email protected] QAContact|[email protected] | --- Comment #45 from Chen Congwu <[email protected]> 2010-04-15 21:48:56 PST --- (In reply to comment #43) > (In reply to comment #42) > [naming of config based on DevInf] > > Depending on extract information from DevInf looks to me not work well: > > 1) Will the peer always send its DevInf? > > If not, Synthesis will request it. That's why I said that the information > should be available after a sync, but cannot necessarily be extracted from the > first message. > > Of course, there will be clients which have no DevInf at all (which I find > unlikely) or no useful information inside. > > > 2) Will the DevInf be meaningful? For example, we have seen Nokia N900 as > > 'Nokia Nxx', that seems to me not make sense. > > I still think we need to find other ways to notify the client.. > > Suggestions welcome, of course. Since I don't think we can figure out that automatically, we still need some user intervention, isn't it? Extracting information from DevInf might also needs same tricks/hacks as I already had with 'Authentication failure detection' patch which was not nice. Can we ask the user provide this information when he starts the sync? For example, can we reuse 'deviceID' for that purpose? Or some other field in SyncML? -- 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
