[Bug 26866] Conn.I.Addressing etc. — requesting handles for a vCard field or URI

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26866

--- Comment #73 from Andre Moreira Magalhaes <andrunko at gmail.com> 2012-02-14 06:41:42 PST ---
(In reply to comment #72)
> Created attachment 57037 [details] [review]
> Undraft Conn.I.Addressing
> 
> ---
> 
> Any objection?

Hmm, I have some things I would like to discuss first.

tp-qt 0.9.0 supports Conn.I.Addressing.DRAFT from tp-spec 0.25.1. As the interface was draft we only generate internal low-level proxies (not exported).
I see now that the current spec release contains Conn.I.Addressing1 instead (not support by tp-qt).

The problem is that we haven't decided what to do with versioned interfaces.
Should we make the generated proxies public? The generate class is named ConnectionInterfaceAddressingInterface (not including the version number). What if the
interface changes to Addressing2 and breaks API? Should we generate the class as ConnectionInterfaceAddressing1Interface instead so we can generate both when
Addressing2 is around? Or should we make all versioned interfaces internal now, much like what we do for DRAFT interfaces?
Or should we just ignore the versioning and make it public and hope for the best.

We would also have issues with the high-level API when/if versioned interfaces changes, as the changes may affect high-level public API (we could deprecate
them if needed, but still an "issue").

Note that this is important for all versioned interfaces, not only this one.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.