[Gossip-dev] "id" account param and property

Xavier Claessens xclaesse at gmail.com
Sat Jan 6 17:13:30 CET 2007


Hi all,

It seems gossip is a bit confused. There is 2 different "id" for an
account, a static property and a dynamic parameter. We shouldn't mix
them up, here is what is the meaning of each:

1) The "id" property is static, we can assume it's not NULL and
different for all account of a given protocol. We can have a jabber
account with id=test at gmail.com and an MSN account with the same ID, but
not 2 accounts with the same ID for the same protocol. So the pair
protocol+account_id_property is unique. The "id" property should be set
by the backend *after* the account is connected ! For link-local
accounts we get an id after the account is connected using telepathy
branch (am I wrong here ?). So this shouldn't be used for connecting the
account, the backend should take the "id" parameter to connect. In most
cases (jabber, msn) the backend will set account's id property to the
same value than the account parameter once the account is connected.

2) The "id" account parameter is dynamic, we can't assume it's not NULL,
we can't even assume it exists (link local doesn't have an account ID).
It's used by many protocols to connect the account, but not always.
Telepathy spec says this parameter should be named "account" and not
"id" as gossip does atm, I think we should change that to be less
confusing.

In both cases we can't assume "id" is structured like
"user at server/resource".

I know the distinction is useless for the jabber backend, the "id"
property and parameter will always be the same, but that's important
when using telepathy backend with link-local protocols. So I think the
jabber backend should also follow those rules to not be confusing.

I'll try to fix places where gossip uses the wrong "id".

Xavier Claessens.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.imendio.com/pipermail/gossip-dev/attachments/20070106/f6945363/attachment.pgp


More information about the Gossip-dev mailing list