Re: How does epiphany read its configuration?

On Mon, Sep 10, 2018 at 11:46:56PM +0300, Adrian Perez de Castro wrote:
> > Interestingly, epiphany can read dconf settings, but not write...
> 
> Writes to configuration are done through D-Bus to avoid race conditions which
> may arise when more than a process is trying to write the same setting: this
> ensures that concurrent access is never done because requests coming from the
> bud are handled serially. Also, D-Bus is used to notify of settings updates,
> so it just fits well that all writes go through a single place.
> 
> FWIW, reading is done directly by each process because fetching settings is
> a much more common operation, often done repeatedly, and in that case it makes
> sense to avoid a roundtrip through D-Bus.

Ah, OK. That makes sense. Thanks for explaining it so well!

Cheers,
L.

-- 
Leonid Isaev