[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Service refactoring
From: |
Ludovic Courtès |
Subject: |
Re: Service refactoring |
Date: |
Thu, 10 Sep 2015 18:05:07 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
Mark H Weaver <address@hidden> skribis:
> Will we ever encounter a case where two services need to be told about
> each other? More generally, the "needs to know about" graph might
> contain cycles. Even if there's not one today, we may encounter one
> tomorrow. I don't see a compelling reason to restrict this structure to
> be a DAG, and such a restriction may cause problems for us later.
I can’t think of any pair of services that “extend” each other, but I’ll
keep that in mind.
Thanks,
Ludo’.
- [PATCHES] Get elogind-service working as intended, Mark H Weaver, 2015/09/03
- Re: Service refactoring, Ludovic Courtès, 2015/09/20
- Re: Service refactoring, Andy Wingo, 2015/09/21
- Re: Service refactoring, Ludovic Courtès, 2015/09/21
- Re: Service refactoring, Thompson, David, 2015/09/23
- Re: Service refactoring, Ludovic Courtès, 2015/09/24
- Re: Service refactoring, 宋文武, 2015/09/24
- Re: Service refactoring, Ludovic Courtès, 2015/09/24
- Re: Service refactoring, Christopher Allan Webber, 2015/09/25
- Re: Service refactoring, Ludovic Courtès, 2015/09/26