Stream: IG creation
Topic: Communication threads
Ole Hedegaard (Oct 09 2019 at 12:31):
Hi,
We have a UI client using the Communication resource as a basis for "mailbox" functionality. To that end they need some way of organising messages into logical "threads" (time based as eg. Outlook). Is there any recommended way of doing that? In principle the "inResponseTo" field can chain related messages, but digging up an entire thread would require a lot of roundtrips to the server. Any other recommended way of correlating messages?
Thanks,
Ole
Lloyd McKenzie (Oct 09 2019 at 15:12):
That would be the primary mechanism. You could also add a "thread id" extension and make it searchable (if the software involved has a sense of a thread being created). As a poor-man's thread id, you could also define a "smart" search on subject that matches on subject, ignoring prefixes like fwd: and re: (or not being so smart if those prefixes aren't things that even need to be worried about)
Jens Villadsen (Oct 23 2019 at 10:37):
@Ole Hedegaard FYI: inResponseTo is part of R4 (and probably onwards)
Josh Mandel (Oct 23 2019 at 15:40):
inResponseTo is multiple cardinality -- so it'd be possible to define a convention where every message in a thread includes the original message of the thread in its inResponseTo array. Not sure I like this, but it fits with the defined semantics and allows an easy search for "all messages in thread" (er, it would if we had a search parameter for inResponseTo).
Last updated: Apr 12 2022 at 19:14 UTC
