Kolab Systems is thinking of such SQL databases for integration purposes, where the performance penalty now lies within having to use the IMAP protocol to gain access to the underlying metadata (seen status, message indexes) in distributed groupware environments where Cyrus itself is not the only component that needs access to such information (but would still remain authoritative, of course, and would be the only component with write access to most tables). While not necessarily the best approach, it seems worth exploring. Kind regards, Jeroen van Meeuwen -From his Android "Andrà Schild" <andre@xxxxxxxxx> wrote: > Am 22.09.2010 16:17, schrieb Lucas Zinato Carraro: >> For me it would be very interesting a option to save cyrus tables >> in a traditional database. ( mysql, postgresql, etc... ) >Beside "interesting" what would you get for a real benefit from this ? >They are ver verly likely to be slower. > >Andrà > >---- >Cyrus Home Page: http://www.cyrusimap.org/ >List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ ---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
