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

[bugzilla-daemon at freedesktop.org]

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

--- Comment #6 from Will Thompson <will.thompson at collabora.co.uk> 2010-08-03 06:59:49 PDT ---
(In reply to comment #4)
> (In reply to comment #2)
> > • Delete protocol-token from the spec;
> > • Respecify message-token to be whatever the protocol uses as an identifier, if
> > any, which may or may not be globally unique;
> 
> This breaks any client that assumes message-token has its (impossible)
> specified semantics, which if I remember correctly includes Maemo 5's
> rtcom-eventlogger; the ability to backport CMs onto Maemo has been rather
> popular, so this seems a bad idea. I'd be in favour of getting rid of
> message-token from the list entirely, though, replacing it with something like
> this at the end of the list of keys:
> 
>     The key "message-token" is reserved and should not be used.

So the options are:

• rename message-token, and run around changing every CM and every UI, and have
clutter in the spec;
• don't rename it, hacking CMs that are backported to Maemo 5 very slightly.

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