[Citadel Development] Re: CODE FREEZE - RELEASE IMMINENT

2015-04-04 Thread harryc
P.S. I should have added:  the whole 'logging' thing goes away, and the 'CULL' command is a no-op in the HA setup. P.P.S. As I'm a bit late to the citadel world, I actually have no certain idea what anyone who posts here does for work, where in the world they live, or, well, anything.  I gather f

[Citadel Development] Re: CODE FREEZE - RELEASE IMMINENT

2015-04-04 Thread harryc
The beautiful thing about the mariadb/galera multimaster database approach is:  Each cit-server talking to a database server instance --- running on the same box citadel is --- thinks it's the only server running.  The fact that citadel has that wonderful 'go threading' call, and has sorted throu

[Citadel Development] Re: CODE FREEZE - RELEASE IMMINENT

2015-04-04 Thread IGnatius T Foobar
I do understand the whole uptime thing. Remember, I work in the hosting business. I know all about 99.999% SLA's (which somehow seem to be disregarded when Exchange shits the bed -- shouldn't all those people be running something more reliable?) Only problem I can see with a multi-master

[Citadel Development] Re: CODE FREEZE - RELEASE IMMINENT

2015-04-04 Thread harryc
I can understand your perspectives, here's a bit more data my current research on the subject revealed.   1)  DBMAIL. Mentioned above as 'already does this'. I wanted to use it.  Seemed just what the situation called for.  Scratch the surface and you see that it expects something else to access s