I did hesitate to send this, for the sole reason that it proposes additional requirements; but isn't LDAP designed to do exactly what is wanted here? In fact, I was under the (perhaps incorrect) impression that someone was already making progress on an LDAP address book feature. This also has the additional benefit that it can be made compliant with using LDAP address books on userland software (ie: Outlook, Thunderbird, etc.).
<br><br>Unless I miss something, that would provide exactly those features that are being requested.<br><br><div><span class="gmail_quote">On 8/10/06, <b class="gmail_sendername">Thomas Bruederli</b> &lt;<a href="mailto:roundcube@gmail.com">
roundcube@gmail.com</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Eric Stadtherr wrote:<br>&gt; Should rev306 be backed out then? It goes against this concept.
<br>&gt;<br>Well, my explanations haven't been clear enough when I talked to<br>Tobias... I'll take care of that, but it definitely goes against my ideas.<br><br>I don't see any reason to have lots of fields in the database if we
<br>choose a format that can be parsed fast and allows us interchange the<br>data with other formats for import/export/sync. If searching the<br>contacts gets a problem I suggest to create a fulltext index with all<br>field values required for search.
<br><br>Please don't hesitate to post your opinions to the addressbook/database<br>design.<br><br>Regards,<br>Thomas<br><br><br></blockquote></div><br>