>-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of >ext Simon McVittie >Sent: Tuesday, January 29, 2008 3:42 PM >To: [email protected] >Subject: Re: [Telepathy] Account and AccountManager objects > >UpdateAccountConditions (as (Account_Condition[]): Added, > as (Account_Condition[]): Removed) > Tell the account manager that the account conditions in the set Added > are now met (accounts with those requirements may now >attempt to connect), > and the account conditions in the set Removed are no longer met. > > If clients attempt to change automatic account conditions >(as returned by > GetAutomaticConditions), the Account Manager MUST NOT raise >an error, and > MUST change any non-automatic account conditions that are > changed at the same time, but it MAY ignore the attempt to change the > automatic account conditions. > >GetAccountConditions () -> as (Account_Condition[]): Satisfied > Get a list of account conditions that are currently >satisfied (accounts > whose requirements are all contained in the returned list may attempt > to connect). > >Signals >- ------- > >AccountRequirementsUpdated (as: Provided, as: Not_Provided) > The account requirements in the set Provided are now met; >accounts with > those requirements may now attempt to connect. The account >requirements in > the set Not_Provided are no longer provided.
To cover absolutely all possible use cases, we'd need the whole Boolean algebra over conditions. A canonical form could be used to avoid a freeform expression language over DBus. But that can be too much to ask. Best regards, Mikhail _______________________________________________ Telepathy mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/telepathy
