On Thu, 12 Dec 2002, Jure Pecar wrote: > what is the current status of the cyrus 2.2 cvs branch? judging by the cvs > commits lately, there are just various little cleanups here and there ... is > there anything big left on the TODO list for 2.2?
The big one is getting the sieve bytecode support merged in, but that needs to undergo testing that may not be able to happen until late January atleast. In any case, I'm not totally sure this feature will make it anyway. IPv6 support should be in 2.2, and I'm waiting to hear back from Hajimu on a few issues I have with his patch (http://bugzilla.andrew.cmu.edu/show_bug.cgi?id=1651). I'm personally currently working on making ptloader able to take authorization modules (I just finished a first version of it with the AFS PTS backend). This would mean that we could, for example, support LDAP groups. Long-term has this stuff moving into SASL, but atleast not until SASL hits 2.2 (this will happen as the IETF draft SASL API settles down a bit). The AFS stuff should probably hit CVS tomorrow afternoon. As it is, we're in no real rush to get 2.2 out the door, especially since so far the only feature that *might* be useful to us locally is the new mupdate implementation. > my little wish would be the sql cyrusdb interface, discussed here a week or > two ago, even if marked exeprimental or something. I don't think we're really interested in this at all, actually. Adding the SQL layer for key/value pairings just seems pretty lame to me. Those who want a direct interface to cyrus's internal datastructures are asking for trouble anyway, and I suggest they continue to use the IMAP interfaces. The only *possible* advantage I see is it gets cyrus's databases backed up with an SQL database, but since you still have to back up the cyrus datastore anyway, you haven't won anything. -Rob -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456 Research Systems Programmer * /usr/contributed Gatekeeper
