Gajim must be more flexible to transport type determining
Hello! I found that Gajim determine type of transport only by domain name. I propose that Gajim can determine type of transport by disco, for example, I receive this packet on login:
\<iq from='ic.my.net' to='me@my.com/Gajim' type='result' id='Gajim_470'>
\<query xmlns='hxxp://jabber.org/protocol/disco#info'>
\<identity category='gateway' type='icq' name='ICQ Transport'/>
\<feature var='hxxp://jabber.org/protocol/disco'/>
\<feature var='jabber:x:delay'/>
\<feature var='urn:xmpp:receipts'/>
\<feature var='jabber:x:conference'/>
\<feature var='http://jabber.org/protocol/commands'/>
\<feature var='jabber:iq:register'/>
\<feature var='vcard-temp'/>
\<feature var='urn:xmpp:ping'/>
\<feature var='jabber:iq:version'/>
\<feature var='jabber:iq:last'/>
\<feature var='urn:xmpp:time'/>
\<feature var='jabber:iq:gateway'/>
\</query>
\</iq>
As you can see, there is
\<identity category='gateway' type='icq' name='ICQ Transport'/>
, which may be used to determining type. Also, this can be used by get_transport_name_from_jid, for example, Gajim may compare domain name part of jid from my contact, with jid of transport, so I can have transport ic.my.com (from which we receive <identity category='gateway' type='icq' name='ICQ Transport'/>), and contacts like
123@ic.my.com
, and correctly work with them.
PS. Sorry, need to quote example contact jid and change http to hxxp, because of protection