From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] some internal api refactors
Date: Mon, 17 Aug 2009 12:39:57 -0700 [thread overview]
Message-ID: <1250537445-sup-4504@masanjin.net> (raw)
In-Reply-To: <1250461358-sup-7209@zyrg.net>
Reformatted excerpts from Rich Lane's message of 2009-08-16:
> The ThreadSet still needs the ref to do the UI-level threading, right?
> Making it another API call is good as long as that's still taken care
> of.
I'm thinking about moving in the direction where the index is also
responsible for threading (so maybe "index" is not the right term
anymore), so the ThreadSet would just be a static representation of the
thread structure of a set of messages as returned by the index. We'll
see how it develops.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2009-08-17 19:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 20:14 William Morgan
2009-08-12 5:26 ` Rich Lane
2009-08-16 21:44 ` William Morgan
2009-08-16 22:49 ` Rich Lane
2009-08-17 19:39 ` William Morgan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1250537445-sup-4504@masanjin.net \
--to=wmorgan-sup@masanjin.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox