On 30/03/2006, at 7:00 PM, Norman Rasmussen wrote:
On 3/30/06, James Bunton <james@xxxxxxxxxxxx> wrote:
Does the Python Yahoo transport publish itself in service discovery?
yep
Do a disco#info with Psi, and look at the XML console. What
differences
are there between the MSN & Yahoo transports?
<iq from="yahoo.jabber.server" type="result" id="ad40a"
to="me@xxxxxxxxxxxxx/Work" >
<query xmlns="http://jabber.org/protocol/disco#info";>
<identity category="gateway" type="yahoo" name="XMPPPY Yahoo!
Transport (Dev)" />
<feature var="jabber:iq:register" />
<feature var="jabber:iq:version" />
</query>
</iq>
<iq from="msn.jabber.server" type="result" to="me@xxxxxxxxxxxxx/Work"
id="ad3fa" >
<query xmlns="http://jabber.org/protocol/disco#info";>
<identity category="gateway" type="msn" name="MSN Transport" />
<identity category="conference" type="text" name="MSN Transport
Chatrooms" />
<feature var="http://jabber.org/protocol/disco"; />
<feature var="jabber:x:conference" />
<feature var="jabber:iq:conference" />
<feature var="jabber:iq:register" />
<feature var="jabber:iq:gateway" />
<feature var="jabber:iq:version" />
<feature var="http://jabber.org/protocol/commands"; />
<feature var="vcard-temp" />
</query>
</iq>
Looks like jabber:iq:gateway is missing on the yahoo transport, but
that is used to indicate implemenetation of the send "legacy username
to the gateway and receive a properly-formatted JID in return"
process, which is not supposed atm.
What's required to make the webreg work?
--
- Norman Rasmussen
- Email: norman@xxxxxxxxxxxxxxx
- Home page: http://norman.rasmussen.co.za/
The only line part that webreg cares about is the <identity/>. That's
correctly formatted in both stanzas.
Have a look in your config.php file for webreg, make sure you have a
line:
$gateways["yahoo"] = "auto";
Otherwise you don't even get the option to choose to register with the
yahoo gateway.
When your query your jabber server with disco#items, does the Yahoo
transport show up?
Differently to PyMSNt?
---
James
