[Bug 26838] New: define some token or tuple that unambiguously maps to one message

[bugzilla-daemon at freedesktop.org]

http://bugs.freedesktop.org/show_bug.cgi?id=26838

           Summary: define some token or tuple that unambiguously maps to
                    one message
           Product: Telepathy
           Version: git master
          Platform: Other
        OS/Version: All
            Status: ASSIGNED
          Severity: normal
          Priority: medium
         Component: tp-spec
        AssignedTo: simon.mcvittie at collabora.co.uk
        ReportedBy: simon.mcvittie at collabora.co.uk
         QAContact: telepathy-bugs at lists.freedesktop.org
                CC: cosimo.alfarano at collabora.co.uk


In Bug #26785 I wrote, in reply to Cosimo:
> > From this point of view, TP should create its own unique token or give the
> > possibility to clients to obtain a trustable and unique token, even if its
> > uniqueness is only local to TP (ie not passed by the protocol).
>
> What you ideally want for a database is a token that maps 1:1 to an abstract
> message (the "message-token" header in telepathy-spec), but unfortunately
> that's not possible in most protocols. The best we can do is a token such that
> each token uniquely identifies one abstract message, but each abstract message
> might have more than one such token. I can't think of a good name for that
> right now; can you?
>
> Ways the CM could achieve that "next best thing" include:
>
> * put a token with those semantics on each message (i.e. generate a large
>   number of UUIDs)
>
> * put a different UUID on each Channel instance, so that the tuple (channel
>   UUID, pending message ID) is unique over time


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