Michaël Larouche wrote: >I have Telepathy-Gabble that support Jabber and which export the > following parameters for Jabber: >username, password, stun-server, ressource, port, old-ssl, priority and > so on > >Now I have telepathy-libiris that support Jabber and which export the >following parameters for Jabber: >Jid, Password, TransversalServer, Ressource, ConnectionPart, UseTls, >RessourcePriority, etc... > >So you have similar parameters that have different names and case. > >Either >-Ask the connection manager authors to use a standard name scheming for > a given protocol
Suggestion from someone external: Telepathy standardises a set of names that are allowed (like ID, Password, ServerAddress, Resource). If any other parameter is present, it should be prefixed with X-. No *required* key should be prefixed with X-. PS: Separating "address" from "port" is not a good idea. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
pgpqrJiAgNWZY.pgp
Description: PGP signature
_______________________________________________ kopete-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kopete-devel
