[Telepathy] [Bug 14188] New: Invalidate TpChannel objects as soon as their parent TpConnection disconnects

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Jan 21 12:43:33 PST 2008


           Summary: Invalidate TpChannel objects as soon as their parent
                    TpConnection disconnects
           Product: Telepathy
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: major
          Priority: high
         Component: telepathy-glib
        AssignedTo: telepathy at lists.freedesktop.org
        ReportedBy: simon.mcvittie at collabora.co.uk

Before telepathy-glib is released with client code, we need to ensure that
TpChannel objects are invalidated as soon as their parent TpConnection

To be able to get this information, we need to be able to work out what the
parent TpConnection *is*. I don't think the Telepathy spec explicitly
guarantees that you can truncate the object path at an appropriate point, so we
probably need to force the issue by making the user pass a TpConnection to
tp_channel_new() (since you have a channel, you presumably got it from

Otherwise, you'll keep referring to handles which are now completely
meaningless, leading to total reality failure.

Passing a TpConnection to tp_channel_new() would be good future-proofing
anyway, since you can't do anything useful with 90% of our API unless you have
some idea where you're getting handles from, and we want to be able to provide
handle-related convenience API.

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

More information about the Telepathy mailing list