[Telepathy] [Bug 16544] New: Message threading spec
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Fri Jun 27 04:36:15 PDT 2008
http://bugs.freedesktop.org/show_bug.cgi?id=16544
Summary: Message threading spec
Product: Telepathy
Version: unspecified
Platform: Other
OS/Version: All
Status: NEW
Severity: enhancement
Priority: low
Component: telepathy-spec
AssignedTo: telepathy at lists.freedesktop.org
ReportedBy: simon.mcvittie at collabora.co.uk
We've decided to defer more discussion of message threading (like in XEP-201)
until after the "requestotron" (property-based channel requesting interface) is
finished, since it seems to be quite hard.
Issues include:
* how aggressive should UIs be about allocating new thread IDs? If you close an
Empathy chat window/tab and open a new one to the same user, is it a different
thread?
(Sjoerd thinks it probably isn't. Use-case: Sjoerd opens a chat window to talk
to Simon, sends the message "how do you make sbuild work?" (not expecting an
immediate response), and closes the chat window. He then realises he has
something more to say, opens a new chat window to talk to Simon, and sends the
message "never mind, worked it out".)
* should multiple threads really be represented by parallel channels, or should
they be messages tagged with thread IDs within one channel? (The Messages
interface can do this)
* should threads in a MUC chatroom be as separate as threads in a 1-1 chat are?
--
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