[Gossip-dev] Re: [Telepathy] GossipProtocol problems

[Xavier Claessens]

Le dimanche 15 octobre 2006 à 02:07 +0100, Simon McVittie a écrit :
> On Sat, 14 Oct 2006 at 22:20:43 +0200, Xavier Claessens wrote:
> > 3) _register_[account,cancel]: doesn't have an equivalent in telepathy.
> > As I understand teleapthy, accounts have a "register" parameter, is it's
> > set to TRUE we connecting this account, telepathy will automatically
> > register the account.
> 
> Yes. However, you can't rely on this working, even for XMPP (Google
> Talk only accepts registrations over the web, I believe) and other
> protocols might not be able to do in-band registrations at all.
> 
> > 4) _is_valid_username, _get_example_username, _get_default_server and
> > _get_default_port: doesn't seems to have an equivalent in telepathy...
> > maybe it should be added to the specification ?
> 
> The default for anything that has a sensible default can be found in
> ConnectionManager.GetParameters(). Sample values are mentioned in your
> previous mail to the Telepathy list and the replies to it, but I'll repeat
> for the benefit of other Gossip people: we don't have that functionality,
> but perhaps we should.
> 
> Validating parameters as best we can before actually attempting
> registration would perhaps be a nice thing to add too. (I assume you're
> looking for "live" validation as the user types in parameters?)

Yeah would be nice to add a method which gets in argument a dictionary
with all parameters/values and checks if values are correct, then return
a dictionary with incorrect parameters/default-value (or
corrected-value ?)

> > 5) _is_ssl_supported: useless, just check if there is a parameter like
> > "old-ssl" in the account.
> 
> Parameter naming may vary per CM, I think old-ssl is specific to Gabble.
> When we eventually support TLS/SASL for XMPP, things will be somewhat different
> there anyway.

This is mainly used in gossip to know if default port should be 5222 or
5223, but as said somewhere else it can be solved by simply not fill the
port and let the CM set the default value.

> > 6) _send_composing: Don't know if it's supported by telepathy ?!?
> 
> As Daf said, it's not currently, although it's been discussed.
> 
> > 7) _get_active_resource: how can it work with protocols that doesn't
> > support resources ? 
> 
> It can always return a null string, or something? We don't have any
> support for multiple resources in the Telepathy spec at the moment, and
> it will never make sense for many of the non-XMPP protocols.

would be cool to have a spec for this, even if it just returns an empty
list on other protocols than XMPP.

Thanks,

Xavier.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Ceci est une partie de message
	=?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
Url : http://lists.imendio.com/pipermail/gossip-dev/attachments/20061015/7a41384b/attachment.pgp