1. Every time one does a search of the address book the backend performs a PROPFIND. This seems like overkill if the backend already has the contents of the addressbook. In offline mode this doesn't happen, so searches are much faster in offline mode.
2. If the collection contains collections (subfolders) Evolution [which doesn't request the isCollection property] tries to do a GET on these. When the GET fails it just passes over the entry, which is good, but it seems like these could be avoided easily enough. 3. Rather than doing a PROPFIND for ETags to check up-to-date status when not check the ctag of the collection; if that fails fallback to getting the ETag list. 4. And, of course, <https://bugzilla.gnome.org/show_bug.cgi?id=566354>; support for 301 on PUT. Evolution handles an address book with +20,000 entries very gracefully. When I tried this on Thunderbird the entire application was useless after the addressbook was loaded. -- Adam Tauno Williams <awill...@opengroupware.us> _______________________________________________ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers