Re: Proposed module: conduit

[John Stowers <john stowers lists gmail com>]

On Mon, 2008-07-28 at 11:16 -0400, Colin Walters wrote:
> On Mon, 2008-07-28 at 00:32 +0200, Vincent Untz wrote:
> > Homepage: http://www.conduit-project.org
> > svn/git/bzr/...: http://svn.gnome.org/viewvc/conduit/
> > Proposal on d-d-l: http://mail.gnome.org/archives/desktop-devel-list/2008-March/msg00320.html
> > License: ??? (GPLv2 or later?)
> > 
> > Short description:
> > ==================
> > Conduit is a synchronization architecture for the GNOME desktop. It
> > provides an intuitive GUI for synchronizing things and a DBus interface
> > for external applications to do the same.
> 
> I've briefly looked at conduit-0.3.11.1-1.fc9.noarch; one thing I'm
> wondering is that are we thinking of running it by default?  Concretely
> what is a new user's interface to this system?  Just a new entry in the
> Accessories menu?  

If another app calls into conduit using dbus, it will automatically
start, without the gui. If the user then starts Conduit from the
accessories menu, the Gui will be launched atop the already running
service.

Basically I would prefer Conduit did not automatically start with the
session as it increases login time.

There was originally a technical justification for having Conduit
running all the time, but since then we have got better about scanning
for appropriate connected hardware, instead of relying on Conduit
running all the time to notice when it gets plugged in.

In future there may be additional reasons to have conduit running all
the time, such as 'always up to date' sync (only our gconf sync uses
this ATM, IIRC).

In summary however, If I was a distributor, I would not autostart
conduit at login (yet).

John

> 
> 
> _______________________________________________
> desktop-devel-list mailing list
> desktop-devel-list gnome org
> http://mail.gnome.org/mailman/listinfo/desktop-devel-list