http://bugzilla.moblin.org/show_bug.cgi?id=7838





--- Comment #41 from pohly <[email protected]>  2010-04-15 02:32:40 PST ---
(In reply to comment #40)
> (In reply to comment #39)
> 
> > > I tend to prefer solution 1, although it might be worth asking on the 
> > > mailing
> > > list.
> > I like solution 1 too, such credential is part of HTTP server I think. 
> 
> This is implemented.

Comments on the patch, please update:


-usage =  """usage: %prog http://localhost:<port>/<path>
+usage =  """usage: %prog http://localhost:<port>/<path -u username -p
password>

Note that the options were inserted inside <path>. Besides, they shouldn't be
listed here. The Python modules does that for us. Please use
   usage: %prog <options> http://localhost:<port>/<path>

The documentation for the new options also needs a clarification:
   help = "The user name accepted by the server"
should become:
   help = "The user name checked by by the server when an unknown client
connects. Only if the client provides the right credentials, will a new
configuration be created for it automatically, using these credentials."

> > > > > - What is the naming of the new configs?
> > > > The name is 'deviceID-time', any better ideas?
> > > 
> > > Can we compose the name from manufacturer + model? That may only work 
> > > after
> > > completing the sync and thus would depend on renaming the config.
> > That still may not be unique, so we still have to append some string to 
> > make it
> > unique.. I think the real problem is we should found a way to notify the 
> > user
> > we have created a configuration named xxx for the client, so that he
> > understands the configuration name.
> This is still open. Any comments?

We cannot notify the client. Printing a message to the screen in
syncevo-dbus-server or writing into a log also doesn't help much. Therefore I
think we need meaningful names so that a server user can list configs and
recognize which ones where created for him for which device.

I agree that renaming the config has issues, but it seems to me to be the least
evil one. Perhaps we can also rename the logdir used by the initial successful
session at the end of the session? Note that the Synthesis engine should better
be shut down at that point, because it would continue using the old log dir
path.

-- 
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

Reply via email to