[Telepathy] Folks status, the addressbook problem
philip at tecnocode.co.uk
Thu Nov 1 14:19:06 PDT 2012
On Thu, 2012-11-01 at 11:46 -0700, Travis Reitter wrote:
> On Tue, 2012-10-30 at 17:47 +0100, Xavier Claessens wrote:
> > Le mardi 30 octobre 2012 à 15:57 +0000, Simon McVittie a écrit :
> > > On 30/10/12 14:40, Xavier Claessens wrote:
> > > > 2) The Chat/Call/FileTransfer/etch apps, they need to load only one, or small
> > > > subset of individuals.
> > >
> > > This leads to a new API-use-case apart from the two queries you named
> > > (individual -> all personas and persona -> individual): "tell me about
> > > the persona(s) whose XMPP JID(s) is/are smcv at example.com, as quickly as
> > > possible".
> > In this case, the app should have a TpContact and wants an individual
> > for it. From a TpContact folks can construct a persona uid like
> > "telepathy:<account path>:<contact id>", and the DB must then answer the
> > question "what's the individual uid for this persona uid?" and a 2nd
> > question "what's all the personas uid for this individual uid?". Maybe
> > an sqlite DB can answer those 2 questions in one query?
> I'm 99% sure we have a fast way to do this already, whether through a
> data member or method, though I can't find it with a quick skimming of
> the API (which may be a problem in itself).
> Philip, Jeremy, maybe you know what I'm referring to?
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.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 230 bytes
Desc: This is a digitally signed message part
More information about the telepathy