Ondřej Surý wrote:
And the last interesting alternative might be LevelDB by Google:
https://code.google.com/p/leveldb/
But it cannot use a single file, and needs a directory full of files.
And it doesn't actually work, read the riak mailing list and you'll see that
it crashes all the time. And it's written in C++, which will unnecessarily
bloat all of the C-based apps. And, it has no support for multi-process
concurrency, so it would be completely unusable for most Cyrus apps even if it
actually worked as advertised.
O.
On Tue, Jul 2, 2013 at 3:23 PM, Dan White <[email protected]
<mailto:[email protected]>> wrote:
On 07/02/13 09:58 +0200, Ondřej Surý wrote:
Hi,
you might have noticed that Oracle has released Berkeley DB 6.0, and in
unfortunate move they relicensed the BDB to AGPLv3 which makes it
incompatible with anything else than AGPLv3 or GPLv3.
E.g. this makes cyrus licensing incompatible with Berkeley DB 6.0 since
it
would require dual licensing which I hardly think makes sense.
Thus I think it's time to kill the Berkeley DB support in
cyrus-imapd-2.5,
and start thinking about the replacement for cyrus-sasl sasldb (would
skiplist work here? or should we use sqlite3, kyotocabinet or anything
else?).
With regards to cyrus-sasl, Lightining DB is another option:
http://lists.andrew.cmu.edu/__pipermail/cyrus-sasl/2012-__March/002479.html
<http://lists.andrew.cmu.edu/pipermail/cyrus-sasl/2012-March/002479.html>
It's released under the OpenLDAP Public License, which I assume is
compatible since ldapdb is released under the same license.
--
Dan White
--
Ondřej Surý <[email protected] <mailto:[email protected]>>
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
