<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Georg C. F. Greve a écrit :
<blockquote cite="mid:15563186.Att8TR07KJ@katana.lair" type="cite">
<pre wrap="">On Wednesday 30 November 2011 10.18:35 ABBAS Alain wrote:
</pre>
<blockquote type="cite">
<pre wrap="">1) the speed and performance
</pre>
</blockquote>
<pre wrap=""><!---->
This is primarily an issue of using IMAP efficiently, though.
A practical example: The Z-Push backend currently iterates over every
annotation in every folder for both private and shared name spaces one command
at a time, so 2 * n * x commands & responses.
The same can be done in a single command & response.
</pre>
</blockquote>
Tell me with an IMAP search how to have : <br>
I want all event where the event summary contains "kolab"<br>
I want all the contacts where the email or the company contains "Kolab"<br>
?<br>
Imap Efficiently issue ? <br>
<blockquote cite="mid:15563186.Att8TR07KJ@katana.lair" type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">2) not really full search functionnality (try to search for an event for
example without cache who is a really a bad thing on a big calendar (you
must iterate all the mails .....)
</pre>
</blockquote>
<pre wrap=""><!---->
Again: You can search for the event's UID in IMAP, cached by server.
That's not to say there are cases where you want caching for different access
modes, but that is always the case no matter which storage backend is chosen.
</pre>
<blockquote type="cite">
<pre wrap="">3) duplicate info for some groupware object ( not easy without a lot of code
to have for example things like free busy or the status....)
</pre>
</blockquote>
<pre wrap=""><!---->
Virtually every server I know of pre-generates free/busy, and for good
reasons, independently of the storage used, has nothing to do with IMAP.
</pre>
<blockquote type="cite">
<pre wrap="">4) lack on the permissions Impossible to have a granularity like a bdd or
LDAP (example PRivate sensitivity who is just a software bit in the format
we have with imap just
</pre>
</blockquote>
<pre wrap=""><!---->
The more complex ACLs, the more easy to screw it up.
I am not sure I want users to be able to touch anything even remotely as
complex as LDAP ACLs, that would just be inviting accidental leaks and lots of
trouble.
</pre>
<blockquote type="cite">
<pre wrap="">5) buggy duplication info the software must control for example the UID
duplication that is a pain and a lost of time
</pre>
</blockquote>
<pre wrap=""><!---->
Not sure what that is supposed to refer to, but IMAP search makes it trivial
to detect whether two objects have the same UID.
Best regards,
Georg
</pre>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Kolab-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Kolab-devel@kolab.org">Kolab-devel@kolab.org</a>
<a class="moz-txt-link-freetext" href="https://kolab.org/mailman/listinfo/kolab-devel">https://kolab.org/mailman/listinfo/kolab-devel</a></pre>
</blockquote>
<br>
</body>
</html>