[Telepathy] Account conditions overengineered

[mikhail.zabaluev at nokia.com]

>-----Original Message-----
>From: telepathy-bounces at lists.freedesktop.org 
>[mailto:telepathy-bounces at lists.freedesktop.org] On Behalf Of 
>ext Alberto Mardegan
>Sent: Friday, February 08, 2008 3:27 PM
>To: Telepathy
>Subject: Re: [Telepathy] Account conditions overengineered
>
>Ah, now I see that I didn't understand your proposal; so, you mean to
>have only one rule per account, consisting of a list of
>Account_Conditions and Account_Condition_Rules, right?

An account (or a preset) would have a list of Account_Condition_Rules,
which are combined into a logical expression.
The account manager raises or drops Account_Conditions and manages
connections accordingly to the accounts' rules.

>If so, then, you will not be able to express a condition like this:
>connect the account if (A and B) or (C and D), but since I cannot think
>of a single case where we might need similar conditions, I guess we can
>forget about it.

Right.

>>> In the latter proposal, we could combine them so that the 
>conditions 
>>> specified in the .manager and .presets files will be 
>appended to every 
>>> rule specified in the accounts;
>> 
>> I'm wary about such a combination.
>> Let's have the condition parameters override the presets, as 
>do any other account parameters.
>
>If the condition namespaces are the same, yes; but if some condition
>appears in the presets and not in the account, it should be taken into
>consideration, too.

Yes, this requires more thinking; at least a use case could help.

Best regards,
  Mikhail