An analysis about a generic desktop application configuration management system

Daniel Stone daniel at
Tue Apr 12 08:48:40 EEST 2005

On Thu, Jan 01, 1970 at 12:00:00AM +0000, Sean Middleditch wrote:
> Every single use case I can think of where transactions are really
> mandatory aren't for desktop applications, but for system desktop
> services.  Things like configuring the modes in would need
> transactions to avoid frying your monitor.  However, DConf is more
> concerned with stuff like "which of the already configured modes does
> the user want to use" instead of "what are the various parameters of the
> modes."

Right.  It was probably a bad example, but for something like this, you'd
probably want a small shim of a client library which enforced some kind
of policy (or a very sensible server).  The kind of server that lets you
set a mode with a hsync of a bajillion Hz seems like a very badly-written
server anyway. :)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : 

More information about the xdg mailing list