Re: [evolution-patches] patch for #58701 (addressbook)
- From: Chris Toshok <toshok ximian com>
- To: Sivaiah N <snallagatla novell com>
- Cc: evolution-patches lists ximian com
- Subject: Re: [evolution-patches] patch for #58701 (addressbook)
- Date: Tue, 20 Jul 2004 12:33:44 -0700
On Tue, 2004-07-20 at 13:50 +0530, Sivaiah N wrote:
> On Sun, 2004-07-18 at 05:58, Chris Toshok wrote:
> > On Sat, 2004-07-17 at 11:14 +0530, Sivaiah N wrote:
> > > Ok, So in case of *_start_book_view call i don't think it matters
> > > whether backends use e_book_backend_sexp or not as anyway
> > > e_data_book_view_notify_update does the matching by calling
> > > e_book_backend_sexp_match_contact before updating the view
> >
> > Hmm, actually it seems silly to use e_data_book_view_notify_update, as
> > the only thing that can ever happen is an _add from start_book_view, but
> > that's beside the point I suppose.
> >
> > > Groupwise backend does the things similar to file backend both in
> > > start_book_view and get_contact_list methods.
>
> > How does it work? iterate over all contacts on the server? or does it
> > generate a query?
> Actually it maintains summary, so first we see whether it is summary
> query or not. If it is , we search over summary to get ids of the
> matching contacts and get only those contacts from server. Otherwise we
> get all contacts present in the book and
> iterate over them and match against query.
so there's no query language exposed to the client through groupwise?
iterating over the entire addressbook seems like an awfully slow way to
query.
Chris
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]