[Citadel Development] Re: CODE FREEZE - RELEASE IMMINENT

2015-04-03 Thread IGnatius T Foobar
>the idea that you could spread a single Internet domain across a large >group of Citadel servers, and there is still all sorts of bizarre >message routing code to make that happen. ... and this brings up the first bit of axe wielding. Effective immediately, I am removing suppo

[Citadel Development] Re: CODE FREEZE - RELEASE IMMINENT

2015-04-03 Thread IGnatius T Foobar
>I really don't think we should try to fill that gap - since nobody >had scalability issues with citadel so far. Just for failover drdb is >perfect. There was a time when we wanted to try to be an "enterprise" mail/groupware system. That gave rise to the Global Address Book and the i

[Citadel Development] Re: CODE FREEZE - RELEASE IMMINENT

2015-04-03 Thread dothebart
  Fri Apr 03 2015 10:58:37 EDTfrom IGnatius T Foobar @ Uncensored Subject: Re: CODE FREEZE - RELEASE IMMINENT From the very beginning, the idea of a pluggable data store has been part of the architecture. We've done it once -- originally we were using "gdbm" but because that was so unstable we s

[Citadel Development] Re: CODE FREEZE - RELEASE IMMINENT

2015-04-03 Thread IGnatius T Foobar
>From the very beginning, the idea of a pluggable data store has been part of the architecture. We've done it once -- originally we were using "gdbm" but because that was so unstable we switched to Berkeley DB. dothebart would undoubtedly want to use ArangoDB. I'm ok with it as long as i