Hi,
>-----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
>
>Account_Condition: s
> A condition that might be required for an account to be available.
> These may be any UTF-8 string, but they SHOULD be short
>strings of ASCII
> letters, digits, hyphen/minus characters and dots, starting
>with a letter
> or digit.
>
> All conditions not containing a dot are reserved for the Telepathy
> specification. Third-party conditions SHOULD be namespaced
>by a reversed
> domain name, e.g. "com.example.vpn-enabled.head-office".
A string with certain conventions is good enough, but I think there are two
attributes to every condition that might be worthy to separate. One is the
condition type, that could tell a client that this condition is their domain.
Another is the unique tag as such (within the type namespace). For example,
{"org.whatever.vpn", "MyOfficeVPNAccount"}.
It's similar to detailed GObject signals, or XML namespaces.
I think a (type, name) condition tuple could be more convenient than a
syntactic convention on the single ID string, that the clients would have to
parse in order to filter conditions interesting to them.
My two cents,
Mikhail
_______________________________________________
Telepathy mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/telepathy
