Future Ideas wiki page
murch at andrew.cmu.edu
Thu Jan 7 23:31:18 EST 2010
Thanks for adding this to the wiki. As I've said before, I'm
comfortable with most, if not all, of this.
I'm still working on completing the BODYPARTSTRUCTURE piece of
URLAUTH=BINARY in 2.4. I'm trying to decide if I want to search through
the preformatted BODYSTRUCTURE response in cyrus.cache for the requested
part, or re-parse the MIME headers for the requested part on the fly.
Or perhaps there is some other slick way of doing this that hasn't
occurred to me yet.
Bron Gondwana wrote:
> Hi All,
> I've set up a new wiki page here:
> Linked from the roadmap:
> I've updated the Roadmap with the items I have ready right
> now for 2.4, and put everything else into the bright future
> under 2.5 for now, subject to "actually gets finished and
> stable", obviously.
> Most of these ideas have been fleshed out in some detail
> already in my postings to the devel mailing list. Some are
> still a little bit raw (like having the mailbox path on disk
> depend on the uniqueid rather than the actual mailbox name.
> I'll expand on this another time... and it's not yet mentioned
> on the wiki, but it makes a lot of things nicer!)
> Anyway, I'd love feedback on any or all of it, and if there
> are other things that you feel are really important for the
> future viability of Cyrus I'd love to hear about them as well.
> I haven't yet had a chance to look at the QRESYNC stuff that
> Ken's already done for 2.4, and we might wind up releasing
> a 2.4 without a lot of these changes just because there's a
> lot of work in there!
> That said, I'm pushing myself pretty aggressively to have that
> list finished by April of THIS YEAR. Particularly the low
> bandwidth replication, which depends on all pretty much all
> of the others!
> Cyrus-project mailing list
> Cyrus-project at lists.andrew.cmu.edu
Carnegie Mellon University
More information about the Cyrus-devel