[colord] Why is colord a daemon?

Mattias Andrée maandree at member.fsf.org
Mon Apr 13 13:44:48 PDT 2015


On Mon, 13 Apr 2015 21:42:15 +0100
Richard Hughes <hughsient at gmail.com> wrote:

> On 13 April 2015 at 21:37, Mattias Andrée
> <maandree at member.fsf.org> wrote:
> >> Nope. The sensor can only be used by one process at a
> >> time, and so we provide an interface to lock the sensor
> >> before returning results. There are also several ways
> >> to get the sensor readings, so we also abstract all the
> >> grotty details.
> >
> > But that could be done in a spawn process.
> 
> Sure, one that lives for the duration of the sensor being
> locked. It wouldn't help programs like
> gnome-control-center asking questions like "Is there a
> calibration device available right now?" without
> enumerating each device type each time.
> 
> > And I believe it is not necessary but that it could have
> > made for a simpler solution.
> 
> Sure, but please keep in mind I don't add complexity for
> the sake of complexity -- there are a lot of different
> use cases, a lot of different workflows and a lot of
> different legacy standards and code. :)

I meant that I think you might have reduced complexity.

> 
> Richard.



More information about the colord mailing list