Hi, I have created a branch on Folks to propose a more scalable API:
http://git.collabora.co.uk/?p=user/zabaluev/folks.git;a=shortlog;h=refs/heads/views The new classes are only stubs for discussion purposes. The main additions are IndividualList, providing an asynchronously retrieved live view on individuals matching a certain query, and an abstract Query class with some useful subclasses. The intent with queries is to broadly cover a few common cases, keeping the complexity of implementing queries in persona stores under control. For example, there would be only the OR-combining query to match string prefixes, and the matching should be case insensitive. If the clients want more restrictive matching (e.g. if it's in fact a QtMobility Contacts client using their overengineered query structures), they can filter the resulting list. Matching for a phone number is an interesting special case, which needs fuzzier heuristics to be applied and should perhaps ultimately be customizable. The public hash table of individuals in IndividualAggregator can be eventually deprecated, if we want support for more than a few dosen of contacts, and efficiently implement search-oriented backends. Discussion is welcome. Misha _______________________________________________ telepathy mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/telepathy
