[Telepathy] Folks status, the addressbook problem
travis.reitter at collabora.co.uk
Mon Nov 5 09:02:04 PST 2012
On Sat, 2012-11-03 at 16:19 +0000, Philip Withnall wrote:
> On Fri, 2012-11-02 at 09:14 -0700, Travis Reitter wrote:
> > On Fri, 2012-11-02 at 09:52 +0100, Xavier Claessens wrote:
> > > Le jeudi 01 novembre 2012 à 14:24 -0700, Travis Reitter a écrit :
> > > > On Thu, 2012-11-01 at 21:19 +0000, Philip Withnall wrote:
> > > >
> > > > > Are you thinking of Tpf.Persona.dup_for_contact()? It takes a TpContact
> > > > > and spits out a Tpf.Persona. From the Tpf.Persona, you can get a
> > > > > Folks.Individual from its ‘individual’ property.
> > > >
> > > > No, I meant a general any Persona -> their Individual. It's also
> > > > possible that it was something like Persona.uid -> their Individual.
> > >
> > > Afaik you can do that only if you loaded the full aggregator. Which is
> > > IMHO not something we want to do in half a dozen processes.
> > Right. That would be true in any case though - even if we cached all the
> > links in some special DB (it would just load much more quickly).
> > Maybe a link cache is one of the things we need. In the common case, any
> All sounds pretty similar to thoughts I’ve had. A cache should speed
> initial aggregation up, but it can imagine lots of corner-case bugs
> where the cache gets into a stale state.
OK. I've filed bgo#687671 - Add Individual aggregation cache
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 4042 bytes
Desc: not available
More information about the telepathy