[JDEV] AIM Transport & Jabberd 2.0

Robert Norris rob at cataclysm.cx
Sun Nov 30 15:43:14 CST 2003

On Sat, Nov 29, 2003 at 10:34:18PM -0500, Paul Curtis wrote:
> When using AIM with jabberd2, the AIM transport doesn't handle browse 
> packets. In jabberd 1.4.x, this wasn't a problem as you could configure 
> the JSM to respond with browse information as configured in the 
> jabber.xml config file. Jabberd2 doesn't have this capability, and so 
> browsing to AIM will produce an empty list. This is a bit disconcerting 
> to the users, since they cannot browse to register with the transport. 
> MSN is better, as it handles browse packets, and returns a response.

You can configure the transport in the static list in sm.xml like this:

<item category='gateway' type='aim' jid='aim.example.com' name='AIM Transport'>

<ns> is not really documented either. I should add something to sm.xml
about it, as its used for agents compat as well.

I agree that components should provide disco #info for themselves. Most
of the time it will be dead simple - just a static response.


Robert Norris                                       GPG: 1024D/FC18E6C2
Email+Jabber: rob at cataclysm.cx                Web: http://cataclysm.cx/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://mail.jabber.org/pipermail/jdev/attachments/20031201/755dce50/attachment-0002.pgp>

More information about the JDev mailing list