http://bugzilla.moblin.org/show_bug.cgi?id=7838
--- Comment #37 from Chen Congwu <[email protected]> 2010-04-13 19:40:40 PST --- (In reply to comment #36) > (In reply to comment #35) > > Patch in mb7838 (Requires another patch in libsynthesis) > > I need a user-level documentation for this new feature before I can do the > final review and merge. This can be either a README or an addendum (marked as > experimental) to the http://syncevolution.org/development/http-server-howto Let's finalize that here before I update it in the doc. > Key point that I haven't seen discussed is: > - How does the user set up a server so that it > can create new configs correctly? In particular, > which username/password is expected by the server? Using 'SyncEvolution Client' template is enough (of source syncURL should set correctly), username/password was already inside the template. > - What is the naming of the new configs? The name is 'deviceID-time', any better ideas? > > I am OK with adding 'reusale' property in the configuration, if no > > objection I > > will further adapt the test cases for that. > > I'm not sure yet whether we need the property. Can't we just define that > configuration "temporary-config" is "reusable"? That can work if we hook at the end of the first successful session, at which point we have to rename the config from 'temporary-config' to a permanent config for that peer 'deviceID-time' It works but I think renaming a configuration is a bit confusing. > > One problem in checkForLoginSuccess(), I have to call it repeatedly inside > > Session Step loop because If I tested it and the end of the session, the > > script > > context already gone.. > > We are almost done with 1.0. Instead of merging features that few users will > need, I'd rather refine this. Perhaps in 1.1 we'll have server-side status > codes and then don't need hacks. Alright, let's go with the older solution that always create new configs for any new coming client. -- 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
