Re: proposed architecture evolutions for GConf

2006-11-11 Thread Havoc Pennington
Hi, It's very simple: http://www.gnome.org/projects/gconf/plans.html We just need a volunteer to do those *three things* and a whole lot of pain would go away. As a preface to responding to your mail, keep in mind that there are two interface points that need not use the same mechanism: us

Re: proposed architecture evolutions for GConf

2006-11-11 Thread Josselin Mouette
Le samedi 11 novembre 2006 à 09:21 -0600, Joe Baker a écrit : > An example of the model of communications needed is the IMAP IDLE > protocol. Clients have the connection opened up and the server polls > the client when there are changes to the mailstore that they should be > aware of. Multiple

Re: proposed architecture evolutions for GConf

2006-11-11 Thread Joe Baker
Davyd Madeley wrote: > On Sat, 2006-11-11 at 12:02 +0100, Josselin Mouette wrote: > > >> There are several ways to deal with a single-session, single-host >> configuration engine. Real problems arise when the user can log in >> several times on different machines, with a shared filesystem. With

Re: proposed architecture evolutions for GConf

2006-11-11 Thread Loïc Minier
On Sat, Nov 11, 2006, Davyd Madeley wrote: > It is possible to write alternative GConf backends. I recall that Sun > have written one that uses LDAP, its name starts with an A, but I can't > recall what it is. You don't mean evoldap? -- Loïc Minier <[EMAIL PROTECTED]> __

Re: proposed architecture evolutions for GConf

2006-11-11 Thread Davyd Madeley
On Sat, 2006-11-11 at 12:02 +0100, Josselin Mouette wrote: > There are several ways to deal with a single-session, single-host > configuration engine. Real problems arise when the user can log in > several times on different machines, with a shared filesystem. With the > number of corporate users

Re: proposed architecture evolutions for GConf

2006-11-11 Thread Josselin Mouette
Le samedi 11 novembre 2006 à 12:33 +, Emmanuele Bassi a écrit : > no. > > preferences API is not that simple; you end up with a lot of > applications locking and unlocking a single file, By no means am I talking about shipping all configuration in a single file. The GConf tree should be mappe

Re: proposed architecture evolutions for GConf

2006-11-11 Thread Emmanuele Bassi
Hi Josselin; On Sat, 2006-11-11 at 12:02 +0100, Josselin Mouette wrote: > How about forgetting this communication thing? Configuration is stored > in files, we just need to read and write these files. We even have some > decent ways to monitor files now: local using inotify, remote using fam > wi

Re: proposed architecture evolutions for GConf

2006-11-11 Thread Steve Frécinaux
Josselin Mouette wrote: > To achieve this, the first thing to do - and it should have been done > for a long time - is to move the file notification API from gnome-vfs to > glib. I enjoin you to look at the GVFS effort on the gnomevfs-list archives. The idea is basically to write a replacement for

proposed architecture evolutions for GConf

2006-11-11 Thread Josselin Mouette
Hi, being repeatedly faced with trouble about the GConf architecture, I've thought a bit about the global GConf situation, and I'm therefore proposing some improvements I'd like this to be discussed a bit before any code comes up. I'll try to summarize the current situation for those who don't kno