D-Bus services names (KDE.XxxXxx vs telepathy_kde_xxx_xxx)

[Olli Salli]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05.05.2011 17:07, Daniele E. Domenichelli wrote:
> On 05/05/2011 03:00 PM, George Kiagiadakis wrote:
>> We *do* have a convention, and the convention says that d-bus names
>> should be in the form o.f.T.C.KDE.FooBar, so yes, I completely agree
>> about using KDE.CallUi.
> 
> 
> Always about the service name convention... I read some time ago some
> blog post about versioning of the D-Bus services names (just googling I
> found this [1], but I don't remember if it is the one I was thinking about)
> 
> What do you think about using the convention o.f.T.C.KDE.FooBar0 for the
> preview release and then bumping the version number when it is required?
> (for incompatible changes, etc)
> 
> Cheers
>  Daniele
> 
> 

Uh,

those services are implementing the stable Telepathy Client D-Bus APIs.
You aren't going to make incompatible changes to them anyway. I guess
that versioning scheme would be for people who don't have stable
interface specifications, but just implement some ad-hoc API on a
service and change it at will.

Br,
Olli
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJNwtA6AAoJEAQQkupGanj4ufgH/ijz68pyzrk8Sv7+LndIwEBf
xZdMrTwyaueu+yomr9+at3OoIbaViIpV3bqQyyHLzjJ6gv5laEOSfvIeD4tCuxYe
qi8h8c53y/A7fj80G/adhmRH/cPTAb6FT+LlkQK5gSNQRz9eM/28vNkiVfgbncYd
rIGaSFobQQpws+4rEYrkbD053p+/naqGYJMSdFRumkiKYRU4uZMP7SfqJWHITVdY
y33g+wUGGkG8jZC5TG9jDQiIpBcsOMjI+F9usaICI24z9Ti1n3EK3j2Jbmezt9y0
bsaufZg0BYzovCP/RC3uUaQN1XfIut100mSqhQ01hn+1SWBuY0q2jA4wEy4uibY=
=fzHY
-----END PGP SIGNATURE-----